[prev in list] [next in list] [prev in thread] [next in thread] 

List:       geronimo-dev
Subject:    [IMPORTANT] - ci.apache.org and CMS Shutdown end of January 2022
From:       Gavin McDonald <gmcdonald () apache ! org>
Date:       2021-12-31 11:37:51
Message-ID: CAN0Gg1dxv88anayAu1nSurvNh7wWH736adtVovbmntHAvTNrAw () mail ! gmail ! com
[Download RAW message or body]

Hi All,

(This email is BCC many (19) lists, please reply to builds@apache.org only)

Infra has set a FINAL date of January 31st 2022 for the turn off of
ci.apache.org. This includes all of its nodes , of which the CMS node is
one. Therefore the CMS is also going to be gone on the 31st January 2022.

Any project that still uses the CMS in any way shape or form, MUST migrate
to another build and publish method.

Any project using ci.apache.org for the building and testing/publishing of
CI builds MUST also migrate away to another CI - the direct replacement is
ci2.apache.org the new Buildbot 3.2 based instance. Publishing of Javadocs
and versioned websites etc that normally publish to ci.apache.org/projects
will need to migrate their jobs to ci2.apache.org and publish results to
nightlies.apache.org instead (via an rsync step).

Projects have been repeatedly informed of the deprecation of both
ci.apache.org and also the CMS itself, so this notice should not be a
surprise to anybody.

If you don't  have an INFRA ticket already open, or you don't know if there
is an INFRA ticket already open for your project, please open one
immediately so that we can get working on your migration ASAP. One or two
projects I know of have a non-standard setup of publishing and so the
earlier we get started the better.

Below is a list of projects I know to still be using either the CMS (in
whole or in part) and ci.apache.org for CI builds, there may be more.

Projects fully using the CMS
======================

Commons
DB (and subprojects)
Hive
Oozie

Projects partially using the CMS
=========================

Lucene
CXF
Tapestry
Santuario
Geronimo
Nutch

All the above except Nutch I believe are exporting from Confluence and
committing to
svn.apache.org/repos/infra/websites/production/ - I have been working on an
alternate
method that does not involve the CMS agent (or its dependents like
build_external.pl)
CXF and Tapestry at least have INFRA tickets open regarding this.

Projects using ci.apache.org for CI jobs
================================

The Board - board-site build.
Perl/mod_perl - several test builds.
AsterixDB - docs build
HTTPD - test builds
Juddi - Several test builds
OpenJPA - Several test builds
Creadur - Several test builds
JMeter - test builds
OpenNLP - site build ?
Commons - site build ?
Ponymail - site build ?
TrafficServer - Test Build + site build ?
Tapestry - test build

All builds that need migrating can be seen on this page:

https://ci.apache.org/buildslaves

Ok, those are the details, lets get started please people

Oh, and Happy New Year!

Gavin McDonald
Systems Administrator
ASF Infrastructure Team

[Attachment #3 (text/html)]

<div dir="ltr"><br><div>Hi All,</div><div><br></div><div>(This email is BCC many (19) \
lists, please reply to <a href="mailto:builds@apache.org">builds@apache.org</a> \
only)<br></div><br>Infra has set a FINAL date of January 31st 2022 for the turn off \
of <a href="http://ci.apache.org">ci.apache.org</a>. This includes all of its nodes , \
of which the CMS node is one. Therefore the CMS is also going to be gone on the 31st \
January 2022.<br><br>Any project that still uses the CMS in any way shape or form, \
MUST migrate to another build and publish method.<br><br>Any project using <a \
href="http://ci.apache.org">ci.apache.org</a> for the building and testing/publishing \
of CI builds MUST also migrate away to another CI - the direct replacement is <a \
href="http://ci2.apache.org">ci2.apache.org</a> the new Buildbot 3.2 based instance. \
Publishing of Javadocs and versioned websites etc that normally publish to <a \
href="http://ci.apache.org/projects">ci.apache.org/projects</a> will need to migrate \
their jobs to <a href="http://ci2.apache.org">ci2.apache.org</a> and publish results \
to <a href="http://nightlies.apache.org">nightlies.apache.org</a> instead (via an \
rsync step).<br><br>Projects have been repeatedly informed of the deprecation of both \
<a href="http://ci.apache.org">ci.apache.org</a> and also the CMS itself, so this \
notice should not be a surprise to anybody.<br><br>If you don&#39;t   have an INFRA \
ticket already open, or you don&#39;t know if there is an INFRA ticket already open \
for your project, please open one immediately so that we can get working on your \
migration ASAP. One or two projects I know of have a non-standard setup of publishing \
and so the earlier we get started the better.<br><br>Below is a list of projects I \
know to still be using either the CMS (in whole or in part) and <a \
href="http://ci.apache.org">ci.apache.org</a> for CI builds, there may be \
more.<br><br>Projects fully using the \
CMS<br>======================<br><br>Commons<br>DB (and \
subprojects)<br>Hive<br>Oozie<br><br>Projects partially using the \
CMS<br>=========================<br><br>Lucene<br>CXF<br>Tapestry<br>Santuario<br><div>Geronimo</div><div>Nutch<br></div><div><br></div><div>All \
the above except Nutch I believe are exporting from Confluence and committing to \
<br></div><div><a href="http://svn.apache.org/repos/infra/websites/production/">svn.apache.org/repos/infra/websites/production/</a> \
- I have been working on an alternate <br></div><div>method that does not involve the \
CMS agent (or its dependents like <a \
href="http://build_external.pl">build_external.pl</a>)</div><div>CXF and Tapestry at \
least have INFRA tickets open regarding this.</div><div><br></div><div>Projects using \
<a href="http://ci.apache.org">ci.apache.org</a> for CI jobs \
<br></div><div>================================</div><div><br></div><div>The Board - \
board-site build.</div><div>Perl/mod_perl - several test builds.</div><div>AsterixDB \
- docs build</div><div>HTTPD - test builds</div><div>Juddi - Several test \
builds</div><div>OpenJPA - Several test builds</div><div>Creadur - Several test \
builds</div><div>JMeter - test builds</div><div>OpenNLP - site build \
?<br></div><div>Commons - site build ?</div><div>Ponymail - site build \
?</div><div>TrafficServer - Test Build + site build ?</div><div>Tapestry - test \
build</div><div><br></div><div>All builds that need migrating can be seen on this \
page:</div><div><br></div><div><a \
href="https://ci.apache.org/buildslaves">https://ci.apache.org/buildslaves</a></div><div><br></div><div>Ok, \
those are the details, lets get started please people</div><div><br></div><div>Oh, \
and Happy New Year!<br></div><div><br></div>Gavin McDonald<br>Systems \
Administrator<br>ASF Infrastructure Team</div>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic