Fwd: hemera Buildbot Slave being turned off end of month

I see some of our buildbot jobs running hemera. I've got no idea how
buildbot works. Do we need to reconfig something to select another
buildslave? I'm guessing the jobs won't just self-migrate to a new bot?

---------- Forwarded message ----------
From: Gavin McDonald <gavin_at_16degrees.com.au>
Date: Sun, Nov 27, 2016 at 4:39 AM
Subject: Re: hemera Buildbot Slave being turned off end of month
To: builds_at_apache.org

Hi All,

Just a friendly reminder that Hemera will be turned off in 3 days time.

In 2 days time any remaining jobs will be moved to another host, those on
the list currently are:-

odftoolkit-trunk <https://ci.apache.org/builders/odftoolkit-trunk>
openejb-branch31 <https://ci.apache.org/builders/openejb-branch31>
openejb-branch32 <https://ci.apache.org/builders/openejb-branch32>
svn-backport-conflicts-1.7.x <https://ci.apache.org/builders/svn-backport-
conflicts-1.7.x> svn-backport-conflicts-1.8.x <https://ci.apache.org/
builders/svn-backport-conflicts-1.8.x> svn-backport-conflicts-1.9.x <
https://ci.apache.org/builders/svn-backport-conflicts-1.9.x> svn-warnings <
https://ci.apache.org/builders/svn-warnings> tomee-1.7.x-deploy <
https://ci.apache.org/builders/tomee-1.7.x-deploy> tomee-1.7.x-ubuntu <
https://ci.apache.org/builders/tomee-1.7.x-ubuntu> tomee-javaee-api <
https://ci.apache.org/builders/tomee-javaee-api> tomee-patches <
https://ci.apache.org/builders/tomee-patches> tomee-trunk-deploy <
https://ci.apache.org/builders/tomee-trunk-deploy> tomee-trunk-empty-repo <
https://ci.apache.org/builders/tomee-trunk-empty-repo> tomee-trunk-ubuntu <
https://ci.apache.org/builders/tomee-trunk-ubuntu> tomee-trunk-ubuntu-jvm8 <
https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8>

Gav…

> On 7 Nov. 2016, at 9:38 am, Gavin McDonald <gavin_at_16degrees.com.au> wrote:
>
> Hi All,
>
> Hemera [1] one of our oldest build slaves (over 5 years old now), will be
turned off on the 30th November.
>
> It is recommended you move your builds to one of the new puppetised nodes
listed below [2].
> You all have karma to edit your own config files [3] or please do file an
INFRA Jira ticket [4]
> if you need assistance in making the move.
>
> I would advise you start the move NOW so that we can iron out any
wrinkles before Hemera gets
> turned off for good.
>
> Projects who are in the BCC of this mail - you are affected! Please also
reply to builds_at_apache.org <mailto:builds_at_apache.org> list
> only. As previously mentioned you should all have representatives of the
project signed up to the
> builds mailing list. There will be no more mails about this sent direct
to the projects so keep an eye on
> the builds list for updates and discussions. (Other projects affected may
have the same questions as
> you already answered.)
>
> List of affected builds that need to move off of Hemera:-
>
> jmeter-nightly <https://ci.apache.org/builders/jmeter-nightly>
jmeter-nightly-index <https://ci.apache.org/builders/jmeter-nightly-index>
jmeter-trunk <https://ci.apache.org/builders/jmeter-trunk> odftoolkit-trunk
<https://ci.apache.org/builders/odftoolkit-trunk> openejb-branch31 <
https://ci.apache.org/builders/openejb-branch31> openejb-branch32 <
https://ci.apache.org/builders/openejb-branch32>
svn-backport-conflicts-1.7.x <https://ci.apache.org/builders/svn-backport-
conflicts-1.7.x> svn-backport-conflicts-1.8.x <https://ci.apache.org/
builders/svn-backport-conflicts-1.8.x> svn-backport-conflicts-1.9.x <
https://ci.apache.org/builders/svn-backport-conflicts-1.9.x> svn-warnings <
https://ci.apache.org/builders/svn-warnings> tomee-1.7.x-deploy <
https://ci.apache.org/builders/tomee-1.7.x-deploy> tomee-1.7.x-ubuntu <
https://ci.apache.org/builders/tomee-1.7.x-ubuntu> tomee-javaee-api <
https://ci.apache.org/builders/tomee-javaee-api>tomee-patches <
https://ci.apache.org/builders/tomee-patches> tomee-trunk-deploy <
https://ci.apache.org/builders/tomee-trunk-deploy> tomee-trunk-empty-repo <
https://ci.apache.org/builders/tomee-trunk-empty-repo> tomee-trunk-ubuntu <
https://ci.apache.org/builders/tomee-trunk-ubuntu> tomee-trunk-ubuntu-jvm8 <
https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8> wicket-branch-1.3.x
<https://ci.apache.org/builders/wicket-branch-1.3.x> wicket-branch-1.4.x <
https://ci.apache.org/builders/wicket-branch-1.4.x> wicket-branch-1.5.x <
https://ci.apache.org/builders/wicket-branch-1.5.x> wicket-branch-6.x <
https://ci.apache.org/builders/wicket-branch-6.x> wicket-branch-7.x <
https://ci.apache.org/builders/wicket-branch-7.x> wicket-master <
https://ci.apache.org/builders/wicket-master>
>
> [1] - https://ci.apache.org/buildslaves <https://ci.apache.org/buildslaves>
(see the hemera_ubuntu entry)
> [2] - https://ci.apache.org/buildslaves/bb_1604_test_ubuntu <
https://ci.apache.org/buildslaves/bb_1604_test_ubuntu> ;
https://ci.apache.org/buildslaves/bb_slave1_ubuntu <https://ci.apache.org/
buildslaves/bb_slave1_ubuntu> ; https://ci.apache.org/
buildslaves/bb_slave2_ubuntu <https://ci.apache.org/
buildslaves/bb_slave2_ubuntu> ; https://ci.apache.org/
buildslaves/bb_slave3_ubuntu <https://ci.apache.org/
buildslaves/bb_slave3_ubuntu>;
> * I recommend project move to the first mentioned slave - it is a
16.04 LTS puppetised node.
> [3] - https://svn.apache.org/repos/infra/infrastructure/buildbot/
aegis/buildmaster/master1/projects/ <https://svn.apache.org/repos/
infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/>
> [4] - https://issues.apache.org/jira/browse/INFRA/ <
https://issues.apache.org/jira/browse/INFRA/>
>
>
> Any projects still remaining by the 29th November - I will move them
myself so we do not delay in turning off this aged box.
> Thank you all for helping make this a smooth transition.
>
> Gav… (ASF Infra.)
Received on 2016-11-27 17:48:42 CET