Re: [IMPORTANT] - ci.apache.org and CMS Shutdown end of January 2022
On Sun, 16 Jan 2022 at 10:04, Gavin McDonald wrote: > > > > On 2022/01/13 16:52:26 sebb wrote: > > On Thu, 13 Jan 2022 at 16:17, Gavin McDonald wrote: > > > > > > > > > > > > On 2022/01/13 11:29:16 sebb wrote: > > > > On Wed, 12 Jan 2022 at 13:47, Gavin McDonald > > > > wrote: > > > > > > > > > > Ok, like I said, not worried about this for now, something for later, > > > > > for the now, I'd like to know if I can safely remove the rest of the > > > > > CMS parts for commons website. > > > > > > > > What exactly do you mean by the CMS parts? > > > > > > Going all the way back to the initial post in the is thread: > > > > > > > > > [1] - > > > https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/commons.conf > > > > We won't need that once the ci2.a.o version is fully working. > > Looks to be fully working, may I now go ahead? I've already commented it out in the main config. > > > > > .. > > > [2] - https://cms.apache.org/commons/ > > > > No idea what that is. > > This *is* the CMS at its core, everything else is just configurations. > Whenever anyone clicked on the CMS bookmarklet to edit a page, it > sent them here, where they could edit , view, stage and publish. In which case, AFAIK Commons never used it. > > The SSL certificate has expired and it is asking for a login. > > Ok dont worry about it, certain it is not used and I wont be renewing the > cert. > > > > > > > > > > > > > > > > > BTW, I tried to convert the commons parent CI build to buildbot2, but > > > > it has not worked: > > > > Failure 1: conversion tool does not fix workername entries (nor even > > > > warn about them). I chose a random name from the ones already used in > > > > other builds. That at least allowed the job to be registered. > > > > Failure 2: cannot force a build via IRC as the bots are not listening > > > > on the channel > > > > Failure 3: a change to the SVN source does not seem to trigger the job > > > > > > All fixed :) > > > > > > > > > > > > On 2022/01/12 13:27:17 sebb wrote: > > > > > > Yes, all the component POMs will need to be updated. > > > > > > > > > > > > It's possible that there are consequential changes that need to be > > > > > > made as well. > > > > > > There was a long thread about this a while back; I don't remember > > > > > > all > > > > > > the details. > > > > > > > > > > > > There are also Infra changes that have to be made. > > > > > > Historically changes to some ASF website sources have needed manual > > > > > > assistance, so there is potentially extra work for Infra as well the > > > > > > edit to the file(s). > > > > > > > > > > > > Unless it really, really is essential, why make the change? > > > > > > > > > > > > On Wed, 12 Jan 2022 at 13:19, Gavin McDonald > > > > > > wrote: > > > > > > > > > > > > > > And now the results have updated again, I see 45 files on the > > > > > > > Github search. > > > > > > > > > > > > > > On 2022/01/12 13:12:40 Gavin McDonald wrote: > > > > > > > > > > > > > > > > > > > > > > > > On 2022/01/12 12:11:40 sebb wrote: > > > > > > > > > > > > > > > > > > > > > > > > > Or hopefully never, if Infra can be persuaded to keep the SVN > > > > > > > > > location > > > > > > > > > where it is. > > > > > > > > > > > > > > > > > > I have yet to see a convincing reason why it must be dropped. > > > > > > > > > Indeed I have seen reference to the removal being > > > > > > > > > 'self-imposed'. > > > > > > > > > > > > > > > > > > If it is removed, a lot of (unnecessary) work will be involved > > > > > > > > > updating all the POMs. > > > > > > > > > > > > > > > > I see 3 pom.xml files with a mention, and a howto doc > > > > > > > > > > > > > > > > https://github.com/search?q=org%3Aapache+https%3A%2F%2Fsvn.apache.org%2Frepos%2Finfra%2Fwebsites%2Fproduction%2Fcommons%2F&type=code > > > > > > > > > > > > > > > > I see the two scripts at > > > > > > > > https://svn.apache.org/repos/asf/commons/cms-site/trunk/ > > > > > > > > which reference it. > > > > > > > > > > > > > > > > Where else please? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Sebb > > > > > > > > > > HTH > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 2022/01/05 07:46:16 Gilles Sadowski wrote: > > > > > > > > > > > Hi. > > > > > > > > > > > > > > > > > > > > > > Le mer. 5 janv. 2022 à 08:28, Gavin McDonald > > > > > > > > > > > a écrit : > > > > > > > > > > > > > > > > > > > > > > > > Bump > > > > > > > > > > > > > > > > > > > > > > I've seen your post, but I'm missing too much information > > > > > > > > > > > (about why > > > > > > > > > > > the setup is the way it is) to understand its impact, and > > > > > > > > > > > to know what > > > > > > > > > > > actions, if any, should be performed for individual > > > > > > > > > > > components so that > > > > > > > > > > > the current contents (a SVN-controlled "site-content" > > > > > > > > > > > directory) will still > > > > > >
Re: [IMPORTANT] - ci.apache.org and CMS Shutdown end of January 2022
On 2022/01/13 16:52:26 sebb wrote: > On Thu, 13 Jan 2022 at 16:17, Gavin McDonald wrote: > > > > > > > > On 2022/01/13 11:29:16 sebb wrote: > > > On Wed, 12 Jan 2022 at 13:47, Gavin McDonald wrote: > > > > > > > > Ok, like I said, not worried about this for now, something for later, > > > > for the now, I'd like to know if I can safely remove the rest of the > > > > CMS parts for commons website. > > > > > > What exactly do you mean by the CMS parts? > > > > Going all the way back to the initial post in the is thread: > > > > > > [1] - > > https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/commons.conf > > We won't need that once the ci2.a.o version is fully working. Looks to be fully working, may I now go ahead? > > > .. > > [2] - https://cms.apache.org/commons/ > > No idea what that is. This *is* the CMS at its core, everything else is just configurations. Whenever anyone clicked on the CMS bookmarklet to edit a page, it sent them here, where they could edit , view, stage and publish. > The SSL certificate has expired and it is asking for a login. Ok dont worry about it, certain it is not used and I wont be renewing the cert. > > > > > > > > > > > BTW, I tried to convert the commons parent CI build to buildbot2, but > > > it has not worked: > > > Failure 1: conversion tool does not fix workername entries (nor even > > > warn about them). I chose a random name from the ones already used in > > > other builds. That at least allowed the job to be registered. > > > Failure 2: cannot force a build via IRC as the bots are not listening > > > on the channel > > > Failure 3: a change to the SVN source does not seem to trigger the job > > > > All fixed :) > > > > > > > > > On 2022/01/12 13:27:17 sebb wrote: > > > > > Yes, all the component POMs will need to be updated. > > > > > > > > > > It's possible that there are consequential changes that need to be > > > > > made as well. > > > > > There was a long thread about this a while back; I don't remember all > > > > > the details. > > > > > > > > > > There are also Infra changes that have to be made. > > > > > Historically changes to some ASF website sources have needed manual > > > > > assistance, so there is potentially extra work for Infra as well the > > > > > edit to the file(s). > > > > > > > > > > Unless it really, really is essential, why make the change? > > > > > > > > > > On Wed, 12 Jan 2022 at 13:19, Gavin McDonald > > > > > wrote: > > > > > > > > > > > > And now the results have updated again, I see 45 files on the > > > > > > Github search. > > > > > > > > > > > > On 2022/01/12 13:12:40 Gavin McDonald wrote: > > > > > > > > > > > > > > > > > > > > > On 2022/01/12 12:11:40 sebb wrote: > > > > > > > > > > > > > > > > > > > > > > Or hopefully never, if Infra can be persuaded to keep the SVN > > > > > > > > location > > > > > > > > where it is. > > > > > > > > > > > > > > > > I have yet to see a convincing reason why it must be dropped. > > > > > > > > Indeed I have seen reference to the removal being > > > > > > > > 'self-imposed'. > > > > > > > > > > > > > > > > If it is removed, a lot of (unnecessary) work will be involved > > > > > > > > updating all the POMs. > > > > > > > > > > > > > > I see 3 pom.xml files with a mention, and a howto doc > > > > > > > > > > > > > > https://github.com/search?q=org%3Aapache+https%3A%2F%2Fsvn.apache.org%2Frepos%2Finfra%2Fwebsites%2Fproduction%2Fcommons%2F&type=code > > > > > > > > > > > > > > I see the two scripts at > > > > > > > https://svn.apache.org/repos/asf/commons/cms-site/trunk/ > > > > > > > which reference it. > > > > > > > > > > > > > > Where else please? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Sebb > > > > > > > > > HTH > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 2022/01/05 07:46:16 Gilles Sadowski wrote: > > > > > > > > > > Hi. > > > > > > > > > > > > > > > > > > > > Le mer. 5 janv. 2022 à 08:28, Gavin McDonald > > > > > > > > > > a écrit : > > > > > > > > > > > > > > > > > > > > > > Bump > > > > > > > > > > > > > > > > > > > > I've seen your post, but I'm missing too much information > > > > > > > > > > (about why > > > > > > > > > > the setup is the way it is) to understand its impact, and > > > > > > > > > > to know what > > > > > > > > > > actions, if any, should be performed for individual > > > > > > > > > > components so that > > > > > > > > > > the current contents (a SVN-controlled "site-content" > > > > > > > > > > directory) will still > > > > > > > > > > be reachable using an URL like (for "Commons Math"): > > > > > > > > > > https://commons.apache.org/math > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Without an answer I'll have to go ahead. > > > > > > > > > > > > > > > > > > > > Thanks for your help, > > > > > > > > > > Gilles > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 2022/01/01 12:31:37 Gavin McDonald w
Re: [IMPORTANT] - ci.apache.org and CMS Shutdown end of January 2022
On Thu, 13 Jan 2022 at 16:17, Gavin McDonald wrote: > > > > On 2022/01/13 11:29:16 sebb wrote: > > On Wed, 12 Jan 2022 at 13:47, Gavin McDonald wrote: > > > > > > Ok, like I said, not worried about this for now, something for later, for > > > the now, I'd like to know if I can safely remove the rest of the CMS > > > parts for commons website. > > > > What exactly do you mean by the CMS parts? > > Going all the way back to the initial post in the is thread: > > > [1] - > https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/commons.conf We won't need that once the ci2.a.o version is fully working. > .. > [2] - https://cms.apache.org/commons/ No idea what that is. The SSL certificate has expired and it is asking for a login. > > > > > > BTW, I tried to convert the commons parent CI build to buildbot2, but > > it has not worked: > > Failure 1: conversion tool does not fix workername entries (nor even > > warn about them). I chose a random name from the ones already used in > > other builds. That at least allowed the job to be registered. > > Failure 2: cannot force a build via IRC as the bots are not listening > > on the channel > > Failure 3: a change to the SVN source does not seem to trigger the job > > All fixed :) > > > > > > On 2022/01/12 13:27:17 sebb wrote: > > > > Yes, all the component POMs will need to be updated. > > > > > > > > It's possible that there are consequential changes that need to be made > > > > as well. > > > > There was a long thread about this a while back; I don't remember all > > > > the details. > > > > > > > > There are also Infra changes that have to be made. > > > > Historically changes to some ASF website sources have needed manual > > > > assistance, so there is potentially extra work for Infra as well the > > > > edit to the file(s). > > > > > > > > Unless it really, really is essential, why make the change? > > > > > > > > On Wed, 12 Jan 2022 at 13:19, Gavin McDonald > > > > wrote: > > > > > > > > > > And now the results have updated again, I see 45 files on the Github > > > > > search. > > > > > > > > > > On 2022/01/12 13:12:40 Gavin McDonald wrote: > > > > > > > > > > > > > > > > > > On 2022/01/12 12:11:40 sebb wrote: > > > > > > > > > > > > > > > > > > > Or hopefully never, if Infra can be persuaded to keep the SVN > > > > > > > location > > > > > > > where it is. > > > > > > > > > > > > > > I have yet to see a convincing reason why it must be dropped. > > > > > > > Indeed I have seen reference to the removal being 'self-imposed'. > > > > > > > > > > > > > > If it is removed, a lot of (unnecessary) work will be involved > > > > > > > updating all the POMs. > > > > > > > > > > > > I see 3 pom.xml files with a mention, and a howto doc > > > > > > > > > > > > https://github.com/search?q=org%3Aapache+https%3A%2F%2Fsvn.apache.org%2Frepos%2Finfra%2Fwebsites%2Fproduction%2Fcommons%2F&type=code > > > > > > > > > > > > I see the two scripts at > > > > > > https://svn.apache.org/repos/asf/commons/cms-site/trunk/ > > > > > > which reference it. > > > > > > > > > > > > Where else please? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Sebb > > > > > > > > HTH > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 2022/01/05 07:46:16 Gilles Sadowski wrote: > > > > > > > > > Hi. > > > > > > > > > > > > > > > > > > Le mer. 5 janv. 2022 à 08:28, Gavin McDonald > > > > > > > > > a écrit : > > > > > > > > > > > > > > > > > > > > Bump > > > > > > > > > > > > > > > > > > I've seen your post, but I'm missing too much information > > > > > > > > > (about why > > > > > > > > > the setup is the way it is) to understand its impact, and to > > > > > > > > > know what > > > > > > > > > actions, if any, should be performed for individual > > > > > > > > > components so that > > > > > > > > > the current contents (a SVN-controlled "site-content" > > > > > > > > > directory) will still > > > > > > > > > be reachable using an URL like (for "Commons Math"): > > > > > > > > > https://commons.apache.org/math > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Without an answer I'll have to go ahead. > > > > > > > > > > > > > > > > > > Thanks for your help, > > > > > > > > > Gilles > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 2022/01/01 12:31:37 Gavin McDonald wrote: > > > > > > > > > > > Hi All, > > > > > > > > > > > > > > > > > > > > > > Top posting to clarify for Commons. > > > > > > > > > > > > > > > > > > > > > > Jenkins is not involved here. > > > > > > > > > > > > > > > > > > > > > > There is one build job called 'commons-site' > > > > > > > > > > > > > > > > > > > > > > I believe you no longer use it as it hasn't run since > > > > > > > > > > > July 2021 > > > > > > > > > > > > > > > > > > > > > > https://ci.apache.org/builders/commons-site of which the > > > > > > > > > > > config file > > > > > > > > > > > lives at: > > > > > > > > > > > > > > > > > > > > > > [1] - > > > > > >
Re: [IMPORTANT] - ci.apache.org and CMS Shutdown end of January 2022
On 2022/01/13 11:29:16 sebb wrote: > On Wed, 12 Jan 2022 at 13:47, Gavin McDonald wrote: > > > > Ok, like I said, not worried about this for now, something for later, for > > the now, I'd like to know if I can safely remove the rest of the CMS parts > > for commons website. > > What exactly do you mean by the CMS parts? Going all the way back to the initial post in the is thread: [1] - https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/commons.conf .. [2] - https://cms.apache.org/commons/ > > BTW, I tried to convert the commons parent CI build to buildbot2, but > it has not worked: > Failure 1: conversion tool does not fix workername entries (nor even > warn about them). I chose a random name from the ones already used in > other builds. That at least allowed the job to be registered. > Failure 2: cannot force a build via IRC as the bots are not listening > on the channel > Failure 3: a change to the SVN source does not seem to trigger the job All fixed :) > > > On 2022/01/12 13:27:17 sebb wrote: > > > Yes, all the component POMs will need to be updated. > > > > > > It's possible that there are consequential changes that need to be made > > > as well. > > > There was a long thread about this a while back; I don't remember all > > > the details. > > > > > > There are also Infra changes that have to be made. > > > Historically changes to some ASF website sources have needed manual > > > assistance, so there is potentially extra work for Infra as well the > > > edit to the file(s). > > > > > > Unless it really, really is essential, why make the change? > > > > > > On Wed, 12 Jan 2022 at 13:19, Gavin McDonald wrote: > > > > > > > > And now the results have updated again, I see 45 files on the Github > > > > search. > > > > > > > > On 2022/01/12 13:12:40 Gavin McDonald wrote: > > > > > > > > > > > > > > > On 2022/01/12 12:11:40 sebb wrote: > > > > > > > > > > > > > > > > Or hopefully never, if Infra can be persuaded to keep the SVN > > > > > > location > > > > > > where it is. > > > > > > > > > > > > I have yet to see a convincing reason why it must be dropped. > > > > > > Indeed I have seen reference to the removal being 'self-imposed'. > > > > > > > > > > > > If it is removed, a lot of (unnecessary) work will be involved > > > > > > updating all the POMs. > > > > > > > > > > I see 3 pom.xml files with a mention, and a howto doc > > > > > > > > > > https://github.com/search?q=org%3Aapache+https%3A%2F%2Fsvn.apache.org%2Frepos%2Finfra%2Fwebsites%2Fproduction%2Fcommons%2F&type=code > > > > > > > > > > I see the two scripts at > > > > > https://svn.apache.org/repos/asf/commons/cms-site/trunk/ > > > > > which reference it. > > > > > > > > > > Where else please? > > > > > > > > > > > > > > > > > > > > > > > > > > > Sebb > > > > > > > HTH > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 2022/01/05 07:46:16 Gilles Sadowski wrote: > > > > > > > > Hi. > > > > > > > > > > > > > > > > Le mer. 5 janv. 2022 à 08:28, Gavin McDonald > > > > > > > > a écrit : > > > > > > > > > > > > > > > > > > Bump > > > > > > > > > > > > > > > > I've seen your post, but I'm missing too much information > > > > > > > > (about why > > > > > > > > the setup is the way it is) to understand its impact, and to > > > > > > > > know what > > > > > > > > actions, if any, should be performed for individual components > > > > > > > > so that > > > > > > > > the current contents (a SVN-controlled "site-content" > > > > > > > > directory) will still > > > > > > > > be reachable using an URL like (for "Commons Math"): > > > > > > > > https://commons.apache.org/math > > > > > > > > > > > > > > > > > > > > > > > > > > Without an answer I'll have to go ahead. > > > > > > > > > > > > > > > > Thanks for your help, > > > > > > > > Gilles > > > > > > > > > > > > > > > > > > > > > > > > > > On 2022/01/01 12:31:37 Gavin McDonald wrote: > > > > > > > > > > Hi All, > > > > > > > > > > > > > > > > > > > > Top posting to clarify for Commons. > > > > > > > > > > > > > > > > > > > > Jenkins is not involved here. > > > > > > > > > > > > > > > > > > > > There is one build job called 'commons-site' > > > > > > > > > > > > > > > > > > > > I believe you no longer use it as it hasn't run since July > > > > > > > > > > 2021 > > > > > > > > > > > > > > > > > > > > https://ci.apache.org/builders/commons-site of which the > > > > > > > > > > config file > > > > > > > > > > lives at: > > > > > > > > > > > > > > > > > > > > [1] - > > > > > > > > > > https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/commons.conf > > > > > > > > > > > > > > > > > > > > However, there are other settings/files I also need to > > > > > > > > > > clarify. > > > > > > > > > > > > > > > > > > > > You still have a commons cms site area at: > > > > > > > > > > > > > > > > > > > > [2] - https://cms.apache.org/commons/ > > > > > > > > > > > > > > > > > > > > and also a CMS entry i
Re: [IMPORTANT] - ci.apache.org and CMS Shutdown end of January 2022
On Wed, 12 Jan 2022 at 13:47, Gavin McDonald wrote: > > Ok, like I said, not worried about this for now, something for later, for the > now, I'd like to know if I can safely remove the rest of the CMS parts for > commons website. What exactly do you mean by the CMS parts? BTW, I tried to convert the commons parent CI build to buildbot2, but it has not worked: Failure 1: conversion tool does not fix workername entries (nor even warn about them). I chose a random name from the ones already used in other builds. That at least allowed the job to be registered. Failure 2: cannot force a build via IRC as the bots are not listening on the channel Failure 3: a change to the SVN source does not seem to trigger the job > On 2022/01/12 13:27:17 sebb wrote: > > Yes, all the component POMs will need to be updated. > > > > It's possible that there are consequential changes that need to be made as > > well. > > There was a long thread about this a while back; I don't remember all > > the details. > > > > There are also Infra changes that have to be made. > > Historically changes to some ASF website sources have needed manual > > assistance, so there is potentially extra work for Infra as well the > > edit to the file(s). > > > > Unless it really, really is essential, why make the change? > > > > On Wed, 12 Jan 2022 at 13:19, Gavin McDonald wrote: > > > > > > And now the results have updated again, I see 45 files on the Github > > > search. > > > > > > On 2022/01/12 13:12:40 Gavin McDonald wrote: > > > > > > > > > > > > On 2022/01/12 12:11:40 sebb wrote: > > > > > > > > > > > > > Or hopefully never, if Infra can be persuaded to keep the SVN location > > > > > where it is. > > > > > > > > > > I have yet to see a convincing reason why it must be dropped. > > > > > Indeed I have seen reference to the removal being 'self-imposed'. > > > > > > > > > > If it is removed, a lot of (unnecessary) work will be involved > > > > > updating all the POMs. > > > > > > > > I see 3 pom.xml files with a mention, and a howto doc > > > > > > > > https://github.com/search?q=org%3Aapache+https%3A%2F%2Fsvn.apache.org%2Frepos%2Finfra%2Fwebsites%2Fproduction%2Fcommons%2F&type=code > > > > > > > > I see the two scripts at > > > > https://svn.apache.org/repos/asf/commons/cms-site/trunk/ > > > > which reference it. > > > > > > > > Where else please? > > > > > > > > > > > > > > > > > > > > > > Sebb > > > > > > HTH > > > > > > > > > > > > > > > > > > > > > > > > On 2022/01/05 07:46:16 Gilles Sadowski wrote: > > > > > > > Hi. > > > > > > > > > > > > > > Le mer. 5 janv. 2022 à 08:28, Gavin McDonald > > > > > > > a écrit : > > > > > > > > > > > > > > > > Bump > > > > > > > > > > > > > > I've seen your post, but I'm missing too much information (about > > > > > > > why > > > > > > > the setup is the way it is) to understand its impact, and to know > > > > > > > what > > > > > > > actions, if any, should be performed for individual components so > > > > > > > that > > > > > > > the current contents (a SVN-controlled "site-content" directory) > > > > > > > will still > > > > > > > be reachable using an URL like (for "Commons Math"): > > > > > > > https://commons.apache.org/math > > > > > > > > > > > > > > > > > > > > > > > Without an answer I'll have to go ahead. > > > > > > > > > > > > > > Thanks for your help, > > > > > > > Gilles > > > > > > > > > > > > > > > > > > > > > > > On 2022/01/01 12:31:37 Gavin McDonald wrote: > > > > > > > > > Hi All, > > > > > > > > > > > > > > > > > > Top posting to clarify for Commons. > > > > > > > > > > > > > > > > > > Jenkins is not involved here. > > > > > > > > > > > > > > > > > > There is one build job called 'commons-site' > > > > > > > > > > > > > > > > > > I believe you no longer use it as it hasn't run since July > > > > > > > > > 2021 > > > > > > > > > > > > > > > > > > https://ci.apache.org/builders/commons-site of which the > > > > > > > > > config file > > > > > > > > > lives at: > > > > > > > > > > > > > > > > > > [1] - > > > > > > > > > https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/commons.conf > > > > > > > > > > > > > > > > > > However, there are other settings/files I also need to > > > > > > > > > clarify. > > > > > > > > > > > > > > > > > > You still have a commons cms site area at: > > > > > > > > > > > > > > > > > > [2] - https://cms.apache.org/commons/ > > > > > > > > > > > > > > > > > > and also a CMS entry in svnwcsub: > > > > > > > > > > > > > > > > > > [3] - > > > > > > > > > https://github.com/apache/infrastructure-p6/blob/production/modules/svnwcsub/files/svnwcsub.conf#L47 > > > > > > > > > > > > > > > > > > which is related to the content at: > > > > > > > > > > > > > > > > > > [4] - > > > > > > > > > https://svn.apache.org/repos/infra/websites/production/commons/content/ > > > > > > > > > > > > > > > > > > So you can see there are a number of CMS aspects here that > > > > > > > > > need to be > > > > > > > > > resolved. >
Re: [IMPORTANT] - ci.apache.org and CMS Shutdown end of January 2022
Ok, like I said, not worried about this for now, something for later, for the now, I'd like to know if I can safely remove the rest of the CMS parts for commons website. On 2022/01/12 13:27:17 sebb wrote: > Yes, all the component POMs will need to be updated. > > It's possible that there are consequential changes that need to be made as > well. > There was a long thread about this a while back; I don't remember all > the details. > > There are also Infra changes that have to be made. > Historically changes to some ASF website sources have needed manual > assistance, so there is potentially extra work for Infra as well the > edit to the file(s). > > Unless it really, really is essential, why make the change? > > On Wed, 12 Jan 2022 at 13:19, Gavin McDonald wrote: > > > > And now the results have updated again, I see 45 files on the Github search. > > > > On 2022/01/12 13:12:40 Gavin McDonald wrote: > > > > > > > > > On 2022/01/12 12:11:40 sebb wrote: > > > > > > > > > > Or hopefully never, if Infra can be persuaded to keep the SVN location > > > > where it is. > > > > > > > > I have yet to see a convincing reason why it must be dropped. > > > > Indeed I have seen reference to the removal being 'self-imposed'. > > > > > > > > If it is removed, a lot of (unnecessary) work will be involved > > > > updating all the POMs. > > > > > > I see 3 pom.xml files with a mention, and a howto doc > > > > > > https://github.com/search?q=org%3Aapache+https%3A%2F%2Fsvn.apache.org%2Frepos%2Finfra%2Fwebsites%2Fproduction%2Fcommons%2F&type=code > > > > > > I see the two scripts at > > > https://svn.apache.org/repos/asf/commons/cms-site/trunk/ > > > which reference it. > > > > > > Where else please? > > > > > > > > > > > > > > > > > Sebb > > > > > HTH > > > > > > > > > > > > > > > > > > > > On 2022/01/05 07:46:16 Gilles Sadowski wrote: > > > > > > Hi. > > > > > > > > > > > > Le mer. 5 janv. 2022 à 08:28, Gavin McDonald > > > > > > a écrit : > > > > > > > > > > > > > > Bump > > > > > > > > > > > > I've seen your post, but I'm missing too much information (about why > > > > > > the setup is the way it is) to understand its impact, and to know > > > > > > what > > > > > > actions, if any, should be performed for individual components so > > > > > > that > > > > > > the current contents (a SVN-controlled "site-content" directory) > > > > > > will still > > > > > > be reachable using an URL like (for "Commons Math"): > > > > > > https://commons.apache.org/math > > > > > > > > > > > > > > > > > > > > Without an answer I'll have to go ahead. > > > > > > > > > > > > Thanks for your help, > > > > > > Gilles > > > > > > > > > > > > > > > > > > > > On 2022/01/01 12:31:37 Gavin McDonald wrote: > > > > > > > > Hi All, > > > > > > > > > > > > > > > > Top posting to clarify for Commons. > > > > > > > > > > > > > > > > Jenkins is not involved here. > > > > > > > > > > > > > > > > There is one build job called 'commons-site' > > > > > > > > > > > > > > > > I believe you no longer use it as it hasn't run since July 2021 > > > > > > > > > > > > > > > > https://ci.apache.org/builders/commons-site of which the config > > > > > > > > file > > > > > > > > lives at: > > > > > > > > > > > > > > > > [1] - > > > > > > > > https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/commons.conf > > > > > > > > > > > > > > > > However, there are other settings/files I also need to clarify. > > > > > > > > > > > > > > > > You still have a commons cms site area at: > > > > > > > > > > > > > > > > [2] - https://cms.apache.org/commons/ > > > > > > > > > > > > > > > > and also a CMS entry in svnwcsub: > > > > > > > > > > > > > > > > [3] - > > > > > > > > https://github.com/apache/infrastructure-p6/blob/production/modules/svnwcsub/files/svnwcsub.conf#L47 > > > > > > > > > > > > > > > > which is related to the content at: > > > > > > > > > > > > > > > > [4] - > > > > > > > > https://svn.apache.org/repos/infra/websites/production/commons/content/ > > > > > > > > > > > > > > > > So you can see there are a number of CMS aspects here that need > > > > > > > > to be > > > > > > > > resolved. > > > > > > > > > > > > > > > > My understanding is that you no longer need [1] and [2] > > > > > > > > > > > > > > > > You still use [4] to place your generated content and so [3] is > > > > > > > > also needed. > > > > > > > > > > > > > > > > I have mentioned before that the location of [4] - a CMS > > > > > > > > specific location > > > > > > > > - needs to be replaced by an > > > > > > > > 'svn mv' to https://svn.apache.org/repos/infra/sites/ [5] and > > > > > > > > that [3] > > > > > > > > would be updated to point to that location > > > > > > > > instead. Sebb indicated this would be a lot of work and that > > > > > > > > you needed > > > > > > > > time. It has been a while and nothing > > > > > > > > has yet been done. I will allow more time but please understand > > > > > > > > this MUST > > > > > > > > happen. >
Re: [IMPORTANT] - ci.apache.org and CMS Shutdown end of January 2022
Yes, all the component POMs will need to be updated. It's possible that there are consequential changes that need to be made as well. There was a long thread about this a while back; I don't remember all the details. There are also Infra changes that have to be made. Historically changes to some ASF website sources have needed manual assistance, so there is potentially extra work for Infra as well the edit to the file(s). Unless it really, really is essential, why make the change? On Wed, 12 Jan 2022 at 13:19, Gavin McDonald wrote: > > And now the results have updated again, I see 45 files on the Github search. > > On 2022/01/12 13:12:40 Gavin McDonald wrote: > > > > > > On 2022/01/12 12:11:40 sebb wrote: > > > > > > > Or hopefully never, if Infra can be persuaded to keep the SVN location > > > where it is. > > > > > > I have yet to see a convincing reason why it must be dropped. > > > Indeed I have seen reference to the removal being 'self-imposed'. > > > > > > If it is removed, a lot of (unnecessary) work will be involved > > > updating all the POMs. > > > > I see 3 pom.xml files with a mention, and a howto doc > > > > https://github.com/search?q=org%3Aapache+https%3A%2F%2Fsvn.apache.org%2Frepos%2Finfra%2Fwebsites%2Fproduction%2Fcommons%2F&type=code > > > > I see the two scripts at > > https://svn.apache.org/repos/asf/commons/cms-site/trunk/ > > which reference it. > > > > Where else please? > > > > > > > > > > > > Sebb > > > > HTH > > > > > > > > > > > > > > > > On 2022/01/05 07:46:16 Gilles Sadowski wrote: > > > > > Hi. > > > > > > > > > > Le mer. 5 janv. 2022 à 08:28, Gavin McDonald a > > > > > écrit : > > > > > > > > > > > > Bump > > > > > > > > > > I've seen your post, but I'm missing too much information (about why > > > > > the setup is the way it is) to understand its impact, and to know what > > > > > actions, if any, should be performed for individual components so that > > > > > the current contents (a SVN-controlled "site-content" directory) will > > > > > still > > > > > be reachable using an URL like (for "Commons Math"): > > > > > https://commons.apache.org/math > > > > > > > > > > > > > > > > > Without an answer I'll have to go ahead. > > > > > > > > > > Thanks for your help, > > > > > Gilles > > > > > > > > > > > > > > > > > On 2022/01/01 12:31:37 Gavin McDonald wrote: > > > > > > > Hi All, > > > > > > > > > > > > > > Top posting to clarify for Commons. > > > > > > > > > > > > > > Jenkins is not involved here. > > > > > > > > > > > > > > There is one build job called 'commons-site' > > > > > > > > > > > > > > I believe you no longer use it as it hasn't run since July 2021 > > > > > > > > > > > > > > https://ci.apache.org/builders/commons-site of which the config > > > > > > > file > > > > > > > lives at: > > > > > > > > > > > > > > [1] - > > > > > > > https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/commons.conf > > > > > > > > > > > > > > However, there are other settings/files I also need to clarify. > > > > > > > > > > > > > > You still have a commons cms site area at: > > > > > > > > > > > > > > [2] - https://cms.apache.org/commons/ > > > > > > > > > > > > > > and also a CMS entry in svnwcsub: > > > > > > > > > > > > > > [3] - > > > > > > > https://github.com/apache/infrastructure-p6/blob/production/modules/svnwcsub/files/svnwcsub.conf#L47 > > > > > > > > > > > > > > which is related to the content at: > > > > > > > > > > > > > > [4] - > > > > > > > https://svn.apache.org/repos/infra/websites/production/commons/content/ > > > > > > > > > > > > > > So you can see there are a number of CMS aspects here that need > > > > > > > to be > > > > > > > resolved. > > > > > > > > > > > > > > My understanding is that you no longer need [1] and [2] > > > > > > > > > > > > > > You still use [4] to place your generated content and so [3] is > > > > > > > also needed. > > > > > > > > > > > > > > I have mentioned before that the location of [4] - a CMS specific > > > > > > > location > > > > > > > - needs to be replaced by an > > > > > > > 'svn mv' to https://svn.apache.org/repos/infra/sites/ [5] and > > > > > > > that [3] > > > > > > > would be updated to point to that location > > > > > > > instead. Sebb indicated this would be a lot of work and that you > > > > > > > needed > > > > > > > time. It has been a while and nothing > > > > > > > has yet been done. I will allow more time but please understand > > > > > > > this MUST > > > > > > > happen. > > > > > > > > > > > > > > My ask, for this migration period is that may I get confirmation > > > > > > > that [1] > > > > > > > and [2] can be removed/deleted. > > > > > > > > > > > > > > Hope that clarifies. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Sat, Jan 1, 2022 at 2:31 AM Gary Gregory > > > > > > > wrote: > > > > > > > > > > > > > > > On Fri, Dec 31, 2021 at 8:22 PM Gilles Sadowski > > > > > >
Re: [IMPORTANT] - ci.apache.org and CMS Shutdown end of January 2022
And now the results have updated again, I see 45 files on the Github search. On 2022/01/12 13:12:40 Gavin McDonald wrote: > > > On 2022/01/12 12:11:40 sebb wrote: > > > > Or hopefully never, if Infra can be persuaded to keep the SVN location > > where it is. > > > > I have yet to see a convincing reason why it must be dropped. > > Indeed I have seen reference to the removal being 'self-imposed'. > > > > If it is removed, a lot of (unnecessary) work will be involved > > updating all the POMs. > > I see 3 pom.xml files with a mention, and a howto doc > > https://github.com/search?q=org%3Aapache+https%3A%2F%2Fsvn.apache.org%2Frepos%2Finfra%2Fwebsites%2Fproduction%2Fcommons%2F&type=code > > I see the two scripts at > https://svn.apache.org/repos/asf/commons/cms-site/trunk/ > which reference it. > > Where else please? > > > > > > > Sebb > > > HTH > > > > > > > > > > > > On 2022/01/05 07:46:16 Gilles Sadowski wrote: > > > > Hi. > > > > > > > > Le mer. 5 janv. 2022 à 08:28, Gavin McDonald a > > > > écrit : > > > > > > > > > > Bump > > > > > > > > I've seen your post, but I'm missing too much information (about why > > > > the setup is the way it is) to understand its impact, and to know what > > > > actions, if any, should be performed for individual components so that > > > > the current contents (a SVN-controlled "site-content" directory) will > > > > still > > > > be reachable using an URL like (for "Commons Math"): > > > > https://commons.apache.org/math > > > > > > > > > > > > > > Without an answer I'll have to go ahead. > > > > > > > > Thanks for your help, > > > > Gilles > > > > > > > > > > > > > > On 2022/01/01 12:31:37 Gavin McDonald wrote: > > > > > > Hi All, > > > > > > > > > > > > Top posting to clarify for Commons. > > > > > > > > > > > > Jenkins is not involved here. > > > > > > > > > > > > There is one build job called 'commons-site' > > > > > > > > > > > > I believe you no longer use it as it hasn't run since July 2021 > > > > > > > > > > > > https://ci.apache.org/builders/commons-site of which the config file > > > > > > lives at: > > > > > > > > > > > > [1] - > > > > > > https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/commons.conf > > > > > > > > > > > > However, there are other settings/files I also need to clarify. > > > > > > > > > > > > You still have a commons cms site area at: > > > > > > > > > > > > [2] - https://cms.apache.org/commons/ > > > > > > > > > > > > and also a CMS entry in svnwcsub: > > > > > > > > > > > > [3] - > > > > > > https://github.com/apache/infrastructure-p6/blob/production/modules/svnwcsub/files/svnwcsub.conf#L47 > > > > > > > > > > > > which is related to the content at: > > > > > > > > > > > > [4] - > > > > > > https://svn.apache.org/repos/infra/websites/production/commons/content/ > > > > > > > > > > > > So you can see there are a number of CMS aspects here that need to > > > > > > be > > > > > > resolved. > > > > > > > > > > > > My understanding is that you no longer need [1] and [2] > > > > > > > > > > > > You still use [4] to place your generated content and so [3] is > > > > > > also needed. > > > > > > > > > > > > I have mentioned before that the location of [4] - a CMS specific > > > > > > location > > > > > > - needs to be replaced by an > > > > > > 'svn mv' to https://svn.apache.org/repos/infra/sites/ [5] and that > > > > > > [3] > > > > > > would be updated to point to that location > > > > > > instead. Sebb indicated this would be a lot of work and that you > > > > > > needed > > > > > > time. It has been a while and nothing > > > > > > has yet been done. I will allow more time but please understand > > > > > > this MUST > > > > > > happen. > > > > > > > > > > > > My ask, for this migration period is that may I get confirmation > > > > > > that [1] > > > > > > and [2] can be removed/deleted. > > > > > > > > > > > > Hope that clarifies. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Sat, Jan 1, 2022 at 2:31 AM Gary Gregory > > > > > > wrote: > > > > > > > > > > > > > On Fri, Dec 31, 2021 at 8:22 PM Gilles Sadowski > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > Le ven. 31 déc. 2021 à 14:17, Gary Gregory > > > > > > > > a > > > > > > > > écrit : > > > > > > > > > > > > > > > > > > WRT Commons, CI is handled by GitHub actions > > > > > > > > > > > > > > > > Whatever "handled" means here, is the sentence true for > > > > > > > > *all* components? > > > > > > > > > > > > > > > > I thought that "GH actions" was replacing Travis (for some > > > > > > > > components). > > > > > > > > > > > > > > > > > these days so I am not worried > > > > > > > > > about losing ci.a.o. > > > > > > > > > > > > > > > > If "ci" means "Jenkins", then I'm worried about > > > > > > > > Commons Math > > > > > > > > Commons RNG > > > > > > > > Commons Statistics > > > > > > > > Commons Numbers > > > > > > > > Common
Re: [IMPORTANT] - ci.apache.org and CMS Shutdown end of January 2022
On 2022/01/12 12:11:40 sebb wrote: > Or hopefully never, if Infra can be persuaded to keep the SVN location > where it is. > > I have yet to see a convincing reason why it must be dropped. > Indeed I have seen reference to the removal being 'self-imposed'. > > If it is removed, a lot of (unnecessary) work will be involved > updating all the POMs. I see 3 pom.xml files with a mention, and a howto doc https://github.com/search?q=org%3Aapache+https%3A%2F%2Fsvn.apache.org%2Frepos%2Finfra%2Fwebsites%2Fproduction%2Fcommons%2F&type=code I see the two scripts at https://svn.apache.org/repos/asf/commons/cms-site/trunk/ which reference it. Where else please? > > Sebb > > HTH > > > > > > > > On 2022/01/05 07:46:16 Gilles Sadowski wrote: > > > Hi. > > > > > > Le mer. 5 janv. 2022 à 08:28, Gavin McDonald a > > > écrit : > > > > > > > > Bump > > > > > > I've seen your post, but I'm missing too much information (about why > > > the setup is the way it is) to understand its impact, and to know what > > > actions, if any, should be performed for individual components so that > > > the current contents (a SVN-controlled "site-content" directory) will > > > still > > > be reachable using an URL like (for "Commons Math"): > > > https://commons.apache.org/math > > > > > > > > > > > Without an answer I'll have to go ahead. > > > > > > Thanks for your help, > > > Gilles > > > > > > > > > > > On 2022/01/01 12:31:37 Gavin McDonald wrote: > > > > > Hi All, > > > > > > > > > > Top posting to clarify for Commons. > > > > > > > > > > Jenkins is not involved here. > > > > > > > > > > There is one build job called 'commons-site' > > > > > > > > > > I believe you no longer use it as it hasn't run since July 2021 > > > > > > > > > > https://ci.apache.org/builders/commons-site of which the config file > > > > > lives at: > > > > > > > > > > [1] - > > > > > https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/commons.conf > > > > > > > > > > However, there are other settings/files I also need to clarify. > > > > > > > > > > You still have a commons cms site area at: > > > > > > > > > > [2] - https://cms.apache.org/commons/ > > > > > > > > > > and also a CMS entry in svnwcsub: > > > > > > > > > > [3] - > > > > > https://github.com/apache/infrastructure-p6/blob/production/modules/svnwcsub/files/svnwcsub.conf#L47 > > > > > > > > > > which is related to the content at: > > > > > > > > > > [4] - > > > > > https://svn.apache.org/repos/infra/websites/production/commons/content/ > > > > > > > > > > So you can see there are a number of CMS aspects here that need to be > > > > > resolved. > > > > > > > > > > My understanding is that you no longer need [1] and [2] > > > > > > > > > > You still use [4] to place your generated content and so [3] is also > > > > > needed. > > > > > > > > > > I have mentioned before that the location of [4] - a CMS specific > > > > > location > > > > > - needs to be replaced by an > > > > > 'svn mv' to https://svn.apache.org/repos/infra/sites/ [5] and that [3] > > > > > would be updated to point to that location > > > > > instead. Sebb indicated this would be a lot of work and that you > > > > > needed > > > > > time. It has been a while and nothing > > > > > has yet been done. I will allow more time but please understand this > > > > > MUST > > > > > happen. > > > > > > > > > > My ask, for this migration period is that may I get confirmation that > > > > > [1] > > > > > and [2] can be removed/deleted. > > > > > > > > > > Hope that clarifies. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Sat, Jan 1, 2022 at 2:31 AM Gary Gregory > > > > > wrote: > > > > > > > > > > > On Fri, Dec 31, 2021 at 8:22 PM Gilles Sadowski > > > > > > > > > > > > wrote: > > > > > > > > > > > > > Le ven. 31 déc. 2021 à 14:17, Gary Gregory > > > > > > > a > > > > > > > écrit : > > > > > > > > > > > > > > > > WRT Commons, CI is handled by GitHub actions > > > > > > > > > > > > > > Whatever "handled" means here, is the sentence true for > > > > > > > *all* components? > > > > > > > > > > > > > > I thought that "GH actions" was replacing Travis (for some > > > > > > > components). > > > > > > > > > > > > > > > these days so I am not worried > > > > > > > > about losing ci.a.o. > > > > > > > > > > > > > > If "ci" means "Jenkins", then I'm worried about > > > > > > > Commons Math > > > > > > > Commons RNG > > > > > > > Commons Statistics > > > > > > > Commons Numbers > > > > > > > Commons Geometry > > > > > > > > > > > > > > > > > > > Thank you for correcting my "all". I've not tracked the above 5 > > > > > > components > > > > > > for a while. > > > > > > > > > > > > Gary > > > > > > > > > > > > > > > > > > > If "ci" means web site publishing, I've no idea where we are. > > > > > > > Last word (IIRC) was that requesting one git repository for > > > > > > > each component's web site was overkill, and perhaps (?) > > > > > >
Re: [IMPORTANT] - ci.apache.org and CMS Shutdown end of January 2022
On Wed, 12 Jan 2022 at 12:01, Gavin McDonald wrote: > > Hi Gilles, > > I can not pretend to know how all projects and sub-projects at the ASF > publish their websites. > I have a had a look at the Commons page [1] for web publishing and it looks > like all Commons sub-projects under 'proper' do the build via Maven on their > own local machine/vm and upload the results via svn to [2]/ . > > That being the case, I believe all sub-projects of Commons are fine at the > moment , and that what is being deprecated here is the main Commons website > method of publishing. I believe that too to be fine as it has not used the > CMS itself in earnest for quite a while. > > [1] - https://commons.apache.org/site-publish.html > [2] - > https://svn.apache.org/repos/infra/websites/production/commons/content/proper/ > > As mentioned in the initial mail the SVN area at [2] is also going away at > some point being replaced by another SVN area, but that is not urgent today. > When that happens perhaps all you need to do is an svn switch to the new area > and adjust your publishing docs. Or hopefully never, if Infra can be persuaded to keep the SVN location where it is. I have yet to see a convincing reason why it must be dropped. Indeed I have seen reference to the removal being 'self-imposed'. If it is removed, a lot of (unnecessary) work will be involved updating all the POMs. Sebb > HTH > > > > On 2022/01/05 07:46:16 Gilles Sadowski wrote: > > Hi. > > > > Le mer. 5 janv. 2022 à 08:28, Gavin McDonald a écrit > > : > > > > > > Bump > > > > I've seen your post, but I'm missing too much information (about why > > the setup is the way it is) to understand its impact, and to know what > > actions, if any, should be performed for individual components so that > > the current contents (a SVN-controlled "site-content" directory) will still > > be reachable using an URL like (for "Commons Math"): > > https://commons.apache.org/math > > > > > > > > Without an answer I'll have to go ahead. > > > > Thanks for your help, > > Gilles > > > > > > > > On 2022/01/01 12:31:37 Gavin McDonald wrote: > > > > Hi All, > > > > > > > > Top posting to clarify for Commons. > > > > > > > > Jenkins is not involved here. > > > > > > > > There is one build job called 'commons-site' > > > > > > > > I believe you no longer use it as it hasn't run since July 2021 > > > > > > > > https://ci.apache.org/builders/commons-site of which the config file > > > > lives at: > > > > > > > > [1] - > > > > https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/commons.conf > > > > > > > > However, there are other settings/files I also need to clarify. > > > > > > > > You still have a commons cms site area at: > > > > > > > > [2] - https://cms.apache.org/commons/ > > > > > > > > and also a CMS entry in svnwcsub: > > > > > > > > [3] - > > > > https://github.com/apache/infrastructure-p6/blob/production/modules/svnwcsub/files/svnwcsub.conf#L47 > > > > > > > > which is related to the content at: > > > > > > > > [4] - > > > > https://svn.apache.org/repos/infra/websites/production/commons/content/ > > > > > > > > So you can see there are a number of CMS aspects here that need to be > > > > resolved. > > > > > > > > My understanding is that you no longer need [1] and [2] > > > > > > > > You still use [4] to place your generated content and so [3] is also > > > > needed. > > > > > > > > I have mentioned before that the location of [4] - a CMS specific > > > > location > > > > - needs to be replaced by an > > > > 'svn mv' to https://svn.apache.org/repos/infra/sites/ [5] and that [3] > > > > would be updated to point to that location > > > > instead. Sebb indicated this would be a lot of work and that you needed > > > > time. It has been a while and nothing > > > > has yet been done. I will allow more time but please understand this > > > > MUST > > > > happen. > > > > > > > > My ask, for this migration period is that may I get confirmation that > > > > [1] > > > > and [2] can be removed/deleted. > > > > > > > > Hope that clarifies. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Sat, Jan 1, 2022 at 2:31 AM Gary Gregory > > > > wrote: > > > > > > > > > On Fri, Dec 31, 2021 at 8:22 PM Gilles Sadowski > > > > > wrote: > > > > > > > > > > > Le ven. 31 déc. 2021 à 14:17, Gary Gregory > > > > > > a > > > > > > écrit : > > > > > > > > > > > > > > WRT Commons, CI is handled by GitHub actions > > > > > > > > > > > > Whatever "handled" means here, is the sentence true for > > > > > > *all* components? > > > > > > > > > > > > I thought that "GH actions" was replacing Travis (for some > > > > > > components). > > > > > > > > > > > > > these days so I am not worried > > > > > > > about losing ci.a.o. > > > > > > > > > > > > If "ci" means "Jenkins", then I'm worried about > > > > > > Commons Math > > > > > > Commons RNG > > > > > > Commons Statistics > > > > > > Commons Numbers > > > > > > C
Re: [IMPORTANT] - ci.apache.org and CMS Shutdown end of January 2022
Hi Gilles, I can not pretend to know how all projects and sub-projects at the ASF publish their websites. I have a had a look at the Commons page [1] for web publishing and it looks like all Commons sub-projects under 'proper' do the build via Maven on their own local machine/vm and upload the results via svn to [2]/ . That being the case, I believe all sub-projects of Commons are fine at the moment , and that what is being deprecated here is the main Commons website method of publishing. I believe that too to be fine as it has not used the CMS itself in earnest for quite a while. [1] - https://commons.apache.org/site-publish.html [2] - https://svn.apache.org/repos/infra/websites/production/commons/content/proper/ As mentioned in the initial mail the SVN area at [2] is also going away at some point being replaced by another SVN area, but that is not urgent today. When that happens perhaps all you need to do is an svn switch to the new area and adjust your publishing docs. HTH On 2022/01/05 07:46:16 Gilles Sadowski wrote: > Hi. > > Le mer. 5 janv. 2022 à 08:28, Gavin McDonald a écrit : > > > > Bump > > I've seen your post, but I'm missing too much information (about why > the setup is the way it is) to understand its impact, and to know what > actions, if any, should be performed for individual components so that > the current contents (a SVN-controlled "site-content" directory) will still > be reachable using an URL like (for "Commons Math"): > https://commons.apache.org/math > > > > > Without an answer I'll have to go ahead. > > Thanks for your help, > Gilles > > > > > On 2022/01/01 12:31:37 Gavin McDonald wrote: > > > Hi All, > > > > > > Top posting to clarify for Commons. > > > > > > Jenkins is not involved here. > > > > > > There is one build job called 'commons-site' > > > > > > I believe you no longer use it as it hasn't run since July 2021 > > > > > > https://ci.apache.org/builders/commons-site of which the config file > > > lives at: > > > > > > [1] - > > > https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/commons.conf > > > > > > However, there are other settings/files I also need to clarify. > > > > > > You still have a commons cms site area at: > > > > > > [2] - https://cms.apache.org/commons/ > > > > > > and also a CMS entry in svnwcsub: > > > > > > [3] - > > > https://github.com/apache/infrastructure-p6/blob/production/modules/svnwcsub/files/svnwcsub.conf#L47 > > > > > > which is related to the content at: > > > > > > [4] - > > > https://svn.apache.org/repos/infra/websites/production/commons/content/ > > > > > > So you can see there are a number of CMS aspects here that need to be > > > resolved. > > > > > > My understanding is that you no longer need [1] and [2] > > > > > > You still use [4] to place your generated content and so [3] is also > > > needed. > > > > > > I have mentioned before that the location of [4] - a CMS specific location > > > - needs to be replaced by an > > > 'svn mv' to https://svn.apache.org/repos/infra/sites/ [5] and that [3] > > > would be updated to point to that location > > > instead. Sebb indicated this would be a lot of work and that you needed > > > time. It has been a while and nothing > > > has yet been done. I will allow more time but please understand this MUST > > > happen. > > > > > > My ask, for this migration period is that may I get confirmation that [1] > > > and [2] can be removed/deleted. > > > > > > Hope that clarifies. > > > > > > > > > > > > > > > > > > > > > > > > > > > On Sat, Jan 1, 2022 at 2:31 AM Gary Gregory > > > wrote: > > > > > > > On Fri, Dec 31, 2021 at 8:22 PM Gilles Sadowski > > > > wrote: > > > > > > > > > Le ven. 31 déc. 2021 à 14:17, Gary Gregory a > > > > > écrit : > > > > > > > > > > > > WRT Commons, CI is handled by GitHub actions > > > > > > > > > > Whatever "handled" means here, is the sentence true for > > > > > *all* components? > > > > > > > > > > I thought that "GH actions" was replacing Travis (for some > > > > > components). > > > > > > > > > > > these days so I am not worried > > > > > > about losing ci.a.o. > > > > > > > > > > If "ci" means "Jenkins", then I'm worried about > > > > > Commons Math > > > > > Commons RNG > > > > > Commons Statistics > > > > > Commons Numbers > > > > > Commons Geometry > > > > > > > > > > > > > Thank you for correcting my "all". I've not tracked the above 5 > > > > components > > > > for a while. > > > > > > > > Gary > > > > > > > > > > > > > If "ci" means web site publishing, I've no idea where we are. > > > > > Last word (IIRC) was that requesting one git repository for > > > > > each component's web site was overkill, and perhaps (?) > > > > > not necessary. A seeming dissonance with this reminder... > > > > > > > > > > Regards, > > > > > Gilles > > > > > > > > > > > > > > > > > TY > > > > > > Gary > > > > > > > > > > > > On Fri, Dec 31, 2021 at 6:38 AM Gavin McDonald > > > > > > > > > > > wrot
Re: [IMPORTANT] - ci.apache.org and CMS Shutdown end of January 2022
Hi. Le mer. 5 janv. 2022 à 08:28, Gavin McDonald a écrit : > > Bump I've seen your post, but I'm missing too much information (about why the setup is the way it is) to understand its impact, and to know what actions, if any, should be performed for individual components so that the current contents (a SVN-controlled "site-content" directory) will still be reachable using an URL like (for "Commons Math"): https://commons.apache.org/math > > Without an answer I'll have to go ahead. Thanks for your help, Gilles > > On 2022/01/01 12:31:37 Gavin McDonald wrote: > > Hi All, > > > > Top posting to clarify for Commons. > > > > Jenkins is not involved here. > > > > There is one build job called 'commons-site' > > > > I believe you no longer use it as it hasn't run since July 2021 > > > > https://ci.apache.org/builders/commons-site of which the config file > > lives at: > > > > [1] - > > https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/commons.conf > > > > However, there are other settings/files I also need to clarify. > > > > You still have a commons cms site area at: > > > > [2] - https://cms.apache.org/commons/ > > > > and also a CMS entry in svnwcsub: > > > > [3] - > > https://github.com/apache/infrastructure-p6/blob/production/modules/svnwcsub/files/svnwcsub.conf#L47 > > > > which is related to the content at: > > > > [4] - > > https://svn.apache.org/repos/infra/websites/production/commons/content/ > > > > So you can see there are a number of CMS aspects here that need to be > > resolved. > > > > My understanding is that you no longer need [1] and [2] > > > > You still use [4] to place your generated content and so [3] is also needed. > > > > I have mentioned before that the location of [4] - a CMS specific location > > - needs to be replaced by an > > 'svn mv' to https://svn.apache.org/repos/infra/sites/ [5] and that [3] > > would be updated to point to that location > > instead. Sebb indicated this would be a lot of work and that you needed > > time. It has been a while and nothing > > has yet been done. I will allow more time but please understand this MUST > > happen. > > > > My ask, for this migration period is that may I get confirmation that [1] > > and [2] can be removed/deleted. > > > > Hope that clarifies. > > > > > > > > > > > > > > > > > > On Sat, Jan 1, 2022 at 2:31 AM Gary Gregory wrote: > > > > > On Fri, Dec 31, 2021 at 8:22 PM Gilles Sadowski > > > wrote: > > > > > > > Le ven. 31 déc. 2021 à 14:17, Gary Gregory a > > > > écrit : > > > > > > > > > > WRT Commons, CI is handled by GitHub actions > > > > > > > > Whatever "handled" means here, is the sentence true for > > > > *all* components? > > > > > > > > I thought that "GH actions" was replacing Travis (for some > > > > components). > > > > > > > > > these days so I am not worried > > > > > about losing ci.a.o. > > > > > > > > If "ci" means "Jenkins", then I'm worried about > > > > Commons Math > > > > Commons RNG > > > > Commons Statistics > > > > Commons Numbers > > > > Commons Geometry > > > > > > > > > > Thank you for correcting my "all". I've not tracked the above 5 components > > > for a while. > > > > > > Gary > > > > > > > > > > If "ci" means web site publishing, I've no idea where we are. > > > > Last word (IIRC) was that requesting one git repository for > > > > each component's web site was overkill, and perhaps (?) > > > > not necessary. A seeming dissonance with this reminder... > > > > > > > > Regards, > > > > Gilles > > > > > > > > > > > > > > TY > > > > > Gary > > > > > > > > > > On Fri, Dec 31, 2021 at 6:38 AM Gavin McDonald > > > > wrote: > > > > > > > > > > > Hi All, > > > > > > > > > > > > (This email is BCC many (19) lists, please reply to > > > bui...@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 an
Re: [IMPORTANT] - ci.apache.org and CMS Shutdown end of January 2022
Bump Without an answer I'll have to go ahead. On 2022/01/01 12:31:37 Gavin McDonald wrote: > Hi All, > > Top posting to clarify for Commons. > > Jenkins is not involved here. > > There is one build job called 'commons-site' > > I believe you no longer use it as it hasn't run since July 2021 > > https://ci.apache.org/builders/commons-site of which the config file > lives at: > > [1] - > https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/commons.conf > > However, there are other settings/files I also need to clarify. > > You still have a commons cms site area at: > > [2] - https://cms.apache.org/commons/ > > and also a CMS entry in svnwcsub: > > [3] - > https://github.com/apache/infrastructure-p6/blob/production/modules/svnwcsub/files/svnwcsub.conf#L47 > > which is related to the content at: > > [4] - > https://svn.apache.org/repos/infra/websites/production/commons/content/ > > So you can see there are a number of CMS aspects here that need to be > resolved. > > My understanding is that you no longer need [1] and [2] > > You still use [4] to place your generated content and so [3] is also needed. > > I have mentioned before that the location of [4] - a CMS specific location > - needs to be replaced by an > 'svn mv' to https://svn.apache.org/repos/infra/sites/ [5] and that [3] > would be updated to point to that location > instead. Sebb indicated this would be a lot of work and that you needed > time. It has been a while and nothing > has yet been done. I will allow more time but please understand this MUST > happen. > > My ask, for this migration period is that may I get confirmation that [1] > and [2] can be removed/deleted. > > Hope that clarifies. > > > > > > > > > On Sat, Jan 1, 2022 at 2:31 AM Gary Gregory wrote: > > > On Fri, Dec 31, 2021 at 8:22 PM Gilles Sadowski > > wrote: > > > > > Le ven. 31 déc. 2021 à 14:17, Gary Gregory a > > > écrit : > > > > > > > > WRT Commons, CI is handled by GitHub actions > > > > > > Whatever "handled" means here, is the sentence true for > > > *all* components? > > > > > > I thought that "GH actions" was replacing Travis (for some > > > components). > > > > > > > these days so I am not worried > > > > about losing ci.a.o. > > > > > > If "ci" means "Jenkins", then I'm worried about > > > Commons Math > > > Commons RNG > > > Commons Statistics > > > Commons Numbers > > > Commons Geometry > > > > > > > Thank you for correcting my "all". I've not tracked the above 5 components > > for a while. > > > > Gary > > > > > > > If "ci" means web site publishing, I've no idea where we are. > > > Last word (IIRC) was that requesting one git repository for > > > each component's web site was overkill, and perhaps (?) > > > not necessary. A seeming dissonance with this reminder... > > > > > > Regards, > > > Gilles > > > > > > > > > > > TY > > > > Gary > > > > > > > > On Fri, Dec 31, 2021 at 6:38 AM Gavin McDonald > > > wrote: > > > > > > > > > Hi All, > > > > > > > > > > (This email is BCC many (19) lists, please reply to > > bui...@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
Re: [IMPORTANT] - ci.apache.org and CMS Shutdown end of January 2022
Hi All, Top posting to clarify for Commons. Jenkins is not involved here. There is one build job called 'commons-site' I believe you no longer use it as it hasn't run since July 2021 https://ci.apache.org/builders/commons-site of which the config file lives at: [1] - https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/commons.conf However, there are other settings/files I also need to clarify. You still have a commons cms site area at: [2] - https://cms.apache.org/commons/ and also a CMS entry in svnwcsub: [3] - https://github.com/apache/infrastructure-p6/blob/production/modules/svnwcsub/files/svnwcsub.conf#L47 which is related to the content at: [4] - https://svn.apache.org/repos/infra/websites/production/commons/content/ So you can see there are a number of CMS aspects here that need to be resolved. My understanding is that you no longer need [1] and [2] You still use [4] to place your generated content and so [3] is also needed. I have mentioned before that the location of [4] - a CMS specific location - needs to be replaced by an 'svn mv' to https://svn.apache.org/repos/infra/sites/ [5] and that [3] would be updated to point to that location instead. Sebb indicated this would be a lot of work and that you needed time. It has been a while and nothing has yet been done. I will allow more time but please understand this MUST happen. My ask, for this migration period is that may I get confirmation that [1] and [2] can be removed/deleted. Hope that clarifies. On Sat, Jan 1, 2022 at 2:31 AM Gary Gregory wrote: > On Fri, Dec 31, 2021 at 8:22 PM Gilles Sadowski > wrote: > > > Le ven. 31 déc. 2021 à 14:17, Gary Gregory a > > écrit : > > > > > > WRT Commons, CI is handled by GitHub actions > > > > Whatever "handled" means here, is the sentence true for > > *all* components? > > > > I thought that "GH actions" was replacing Travis (for some > > components). > > > > > these days so I am not worried > > > about losing ci.a.o. > > > > If "ci" means "Jenkins", then I'm worried about > > Commons Math > > Commons RNG > > Commons Statistics > > Commons Numbers > > Commons Geometry > > > > Thank you for correcting my "all". I've not tracked the above 5 components > for a while. > > Gary > > > > If "ci" means web site publishing, I've no idea where we are. > > Last word (IIRC) was that requesting one git repository for > > each component's web site was overkill, and perhaps (?) > > not necessary. A seeming dissonance with this reminder... > > > > Regards, > > Gilles > > > > > > > > TY > > > Gary > > > > > > On Fri, Dec 31, 2021 at 6:38 AM Gavin McDonald > > wrote: > > > > > > > Hi All, > > > > > > > > (This email is BCC many (19) lists, please reply to > bui...@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 > > > > al
Re: [IMPORTANT] - ci.apache.org and CMS Shutdown end of January 2022
On Fri, Dec 31, 2021 at 8:22 PM Gilles Sadowski wrote: > Le ven. 31 déc. 2021 à 14:17, Gary Gregory a > écrit : > > > > WRT Commons, CI is handled by GitHub actions > > Whatever "handled" means here, is the sentence true for > *all* components? > > I thought that "GH actions" was replacing Travis (for some > components). > > > these days so I am not worried > > about losing ci.a.o. > > If "ci" means "Jenkins", then I'm worried about > Commons Math > Commons RNG > Commons Statistics > Commons Numbers > Commons Geometry > Thank you for correcting my "all". I've not tracked the above 5 components for a while. Gary > If "ci" means web site publishing, I've no idea where we are. > Last word (IIRC) was that requesting one git repository for > each component's web site was overkill, and perhaps (?) > not necessary. A seeming dissonance with this reminder... > > Regards, > Gilles > > > > > TY > > Gary > > > > On Fri, Dec 31, 2021 at 6:38 AM Gavin McDonald > wrote: > > > > > Hi All, > > > > > > (This email is BCC many (19) lists, please reply to bui...@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 > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
Re: [IMPORTANT] - ci.apache.org and CMS Shutdown end of January 2022
Le ven. 31 déc. 2021 à 14:17, Gary Gregory a écrit : > > WRT Commons, CI is handled by GitHub actions Whatever "handled" means here, is the sentence true for *all* components? I thought that "GH actions" was replacing Travis (for some components). > these days so I am not worried > about losing ci.a.o. If "ci" means "Jenkins", then I'm worried about Commons Math Commons RNG Commons Statistics Commons Numbers Commons Geometry If "ci" means web site publishing, I've no idea where we are. Last word (IIRC) was that requesting one git repository for each component's web site was overkill, and perhaps (?) not necessary. A seeming dissonance with this reminder... Regards, Gilles > > TY > Gary > > On Fri, Dec 31, 2021 at 6:38 AM Gavin McDonald wrote: > > > Hi All, > > > > (This email is BCC many (19) lists, please reply to bui...@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 > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [IMPORTANT] - ci.apache.org and CMS Shutdown end of January 2022
WRT Commons, CI is handled by GitHub actions these days so I am not worried about losing ci.a.o. TY Gary On Fri, Dec 31, 2021 at 6:38 AM Gavin McDonald wrote: > Hi All, > > (This email is BCC many (19) lists, please reply to bui...@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 >
