You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by Karl Wright <da...@gmail.com> on 2020/08/15 14:30:55 UTC
Fwd: Jenkins instance builds.a.o being shut down 22nd August.
Volunteers needed - doesn't look hard, but somebody needs to contact Infra
to request a ManifoldCF folder it sounds like first. Anyone got time
before next weekend? I'm tapped out until very late in the coming week.
Karl
---------- Forwarded message ---------
From: Gavin McDonald <gm...@apache.org>
Date: Sat, Aug 15, 2020 at 8:24 AM
Subject: Jenkins instance builds.a.o being shut down 22nd August.
To: Apache Infrastructure <us...@infra.apache.org>
Hi All PMCs,
As per the many notifications on the builds@a.o mailing list over the last
few weeks; and the big yellow banner notification on builds.a.o instance
itself, Jenkins is due to be turned off.
The original date for turning off the service was 15th August - *Today!* -
However some projects are yet to make the migration to the new server(s)
(either ci-builds.a.o for the majority or ci-hadoop.a.o for Hadoop and
related projects.)
The deadline has - for one time only - been extended to *22nd August* - so
you have 1 more week only to move your jobs.
After that, builds.a.o WILL be turned off for good and the DNS will
redirect to ci-builds.a.o.
Today I will be moving over most of the remaining agents to the new
masters, leaving just a minimal few for those that still need to migrate.
Job config xml files will be saved. However you can always grab them
yourselves at any time.
See the handy script [1] that can help you migrate all jobs at once - take
only 5 minutes! - After which tweaks may need to be done, or in most cases
not.
[1] -
https://cwiki.apache.org/confluence/display/INFRA/Migrating+Jenkins+jobs+from+Jenkins+to+Cloudbees
Please feel free to forward this message to your dev communities. Replies
should go to users@infra.a.o or new questions should go to builds@a.o
RE: Jenkins instance builds.a.o being shut down 22nd August.
Posted by Kishore Kumar <ki...@live.com>.
@Karl Wright<ma...@gmail.com>, I am volunteering. Have create a Infra task for the new folder setup.
Thanks,
Kishore Kumar
-----Original Message-----
From: Karl Wright <da...@gmail.com>
Sent: 15 August 2020 08:01
To: dev <de...@manifoldcf.apache.org>
Subject: Fwd: Jenkins instance builds.a.o being shut down 22nd August.
Volunteers needed - doesn't look hard, but somebody needs to contact Infra to request a ManifoldCF folder it sounds like first. Anyone got time before next weekend? I'm tapped out until very late in the coming week.
Karl
---------- Forwarded message ---------
From: Gavin McDonald <gm...@apache.org>>
Date: Sat, Aug 15, 2020 at 8:24 AM
Subject: Jenkins instance builds.a.o being shut down 22nd August.
To: Apache Infrastructure <us...@infra.apache.org>>
Hi All PMCs,
As per the many notifications on the builds@a.o<ma...@a.o> mailing list over the last few weeks; and the big yellow banner notification on builds.a.o instance itself, Jenkins is due to be turned off.
The original date for turning off the service was 15th August - *Today!* - However some projects are yet to make the migration to the new server(s) (either ci-builds.a.o for the majority or ci-hadoop.a.o for Hadoop and related projects.)
The deadline has - for one time only - been extended to *22nd August* - so you have 1 more week only to move your jobs.
After that, builds.a.o WILL be turned off for good and the DNS will redirect to ci-builds.a.o.
Today I will be moving over most of the remaining agents to the new masters, leaving just a minimal few for those that still need to migrate.
Job config xml files will be saved. However you can always grab them yourselves at any time.
See the handy script [1] that can help you migrate all jobs at once - take only 5 minutes! - After which tweaks may need to be done, or in most cases not.
[1] -
https://cwiki.apache.org/confluence/display/INFRA/Migrating+Jenkins+jobs+from+Jenkins+to+Cloudbees
Please feel free to forward this message to your dev communities. Replies should go to users@infra.a.o<ma...@infra.a.o> or new questions should go to builds@a.o<ma...@a.o>