All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Michael Halstead <michael@yoctoproject.org>
Cc: yocto@yoctoproject.org
Subject: Re: RFC Autobuilder Naming
Date: Mon, 25 Nov 2013 15:01:29 +0000	[thread overview]
Message-ID: <6760837.T0hJxS54r8@helios> (raw)
In-Reply-To: <528FEC3E.8060304@yoctoproject.org>

Hi Michael,

On Friday 22 November 2013 15:43:58 Michael Halstead wrote:
> Currently all builders are simply named ab00-ab13 based on when we
> acquired them. The name doesn't change except for ab01 which has been
> reused on new hardware. As we increase the number of builders and make
> the build process more flexible this becomes inconvenient. I'd like to
> switch to embedding useful information in the name.
> 
> Going forward as I refresh builders I'd like to name them with their
> distro and location.
> 
> For example at OSL:
> 
> fedora19.osl.yoctoproject.org
> fedora20.osl.yoctoproject.org
> opensuse131.osl.yoctoproject.org
> ubuntu1310.osl.yoctoproject.org
> etc.
> 
> And if we added a build clusters in the EasyStreet datacenter in Portland:
> 
> centos64.pdx.yoctoproject.org
> debian7.pdx.yoctoproject.org
> etc.
> 
> This allows for additional build clusters to be added and makes the
> distro clear to anyone viewing the logs. The current available build
> slaves can be found on the relevant cluster's buildbot interface
> (http://autobuilder.yoctoproject.org/main/buildslaves) so as names
> change there is an easy place to look them up.
> 
> Comments?

I guess this works fine until you want to have two builders with the same 
distro. Maybe we plan not to do that anymore...?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-11-25 15:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22 23:43 RFC Autobuilder Naming Michael Halstead
2013-11-25 15:01 ` Paul Eggleton [this message]
2013-11-25 17:13   ` Michael Halstead
2013-12-03 15:47     ` Flanagan, Elizabeth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6760837.T0hJxS54r8@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=michael@yoctoproject.org \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.