Fwd: hemera Buildbot Slave being turned off end of month

[Gavin McDonald <ga...@16degrees.com.au>]

> Begin forwarded message:
> 
> 
> 
> 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@apache.org <ma...@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.)

Re: Fwd: hemera Buildbot Slave being turned off end of month

[Daniel Shahaf <d....@daniel.shahaf.name>]

Gavin McDonald wrote on Mon, Nov 07, 2016 at 10:50:10 +1100:
> > 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>

These three still use �SVN=/home/danielsh/src/svn/subversion-1.8.0/b/subversion/svn/svn�
in their build configuration.  When they migrate to a new box, that
variable should simply be removed.

(These builders still use backport.pl; they should be upgraded to
tools/dist/detect-conflicting-backports.py some day.)

> > svn-warnings <https://ci.apache.org/builders/svn-warnings>

Should migrate cleanly.