On Fri, 31 Dec 2021 at 11:38, Gavin McDonald <gmcdon...@apache.org> wrote: > > 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.
It's all very well forcing projects to use ci2, but it would help if that was fully working. It seems that ci2 does not yet support IRC triggers, thus making it harder to test. [Especially if there are also issues with pubsub triggers.] If IRC is not fixed before the end of January, will ci.a.o still be removed? Sebb P.S. Where was the current lack of IRC on BB2 advertised?
