camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller <>
Subject Fwd: Jobs tied to Jenkins Slaves
Date Mon, 14 Jul 2014 20:30:58 GMT
I have also updated the Camel Jenkins configuration accordingly.


Software Integration Specialist

Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member

---------- Forwarded message ----------
From: Gavin McDonald <>
Date: Sun, Jul 13, 2014 at 10:02 AM
Subject: Jobs tied to Jenkins Slaves
To: Gavin McDonald <>

Good Day Devs,

Our Jenkins Instance has some slaves being replaced.

Specifically those labelled 'ubuntu[1,2,4,5,6]' are being replaced with
slaves already online called 'ubuntu-[1,2,4,5,6] (notice the dash -).

You are getting this email as at least one of your builds has been
identified as having
been tied to at least one of the slaves due to go off-line next week -
likely Tuesday 15th

Apologies for the short notice on this. Feel free to ping the builds@
mailing list or create
an INFRA jira ticket (component Jenkins) should you have any issues
switching to a new

It is preferred that instead of tieing your build(s) to a particular slave,
that you choose a more
generic label (for Ubuntu slaves choose 'ubuntu or Ubuntu' but if not
please do make sure
you change your config to tie to one of the newer slaves instead.

If by the time we switch off the old slaves and nothing has been done, we
will automatically
change your job configs to point to the generic 'ubuntu' label instead.

Thanks for Listening.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message