Re: [IMPORTANT] - Migration to ci-builds.a.o
Please create a folder for Allura, thanks On 7/16/20 12:33 PM, Gavin McDonald wrote: > Hi All, > > This NOTICE is for everyone on builds.apache.org. We are migrating to a new > Cloudbees based Client Master called https://ci-builds.apache.org. The > migrations of all jobs needs to be done before the switch off date of 15th > August 2020, so you have a maximum of 4 weeks. > > There is no tool or automated way of migrating your jobs, the > differences in the platforms, the plugins and the setup makes it impossible > to do in a safe way. So, you all need to start creating new jobs on > ci-infra.a.o and then , when you are happy, turn off your old builds on > builds.a.o. > > There are currently 4 agents over there ready to take jobs, plus a floating > agent which is shared amongst many masters (more to come). I will migrate > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > will keep an eye of load across both and adjust accordingly. > > If needed, create a ticket on INFRA jira for any issues that crop up, or > email here on builds@a.o. there may be one or two plugins we need to > install/tweak etc. > > We will be not using 'Views' at the top level, but rather we will take > advantage of 'Folders Plus' - each project will get its own Folder and have > authorisation access to create/edit jobs etc within that folder. I will > create these folders as you ask for them to start with. This setup allows > for credentials isolation amongst other benefits, including but not limited > to exclusive agents (Controlled Agents) for your own use , should you have > any project targeted donations of agents. > > As with other aspects of the ASF, projects can choose to just enable all > committers access to their folder, just ask. > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will not > be setting up any forwarding rules or anything like that. > > So, please, get started *now *on this so you can be sure we are all > completed before the final cutoff date of 15th August 2020. > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > tickets. > > Hadoop and related projects have their own migration path to follow, same > cut off date, Cassandra, Beam, CouchDB have already migrated and are doing > very well in their new homes. > > Lets get going ... > -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming <><
Re: [IMPORTANT] - Migration to ci-builds.a.o
Thanks Gavin! Wonderful. I look forward :) On 2020/08/07 08:43:05, Gavin McDonald wrote: > Hi Piotr, > > On Fri, Aug 7, 2020 at 10:10 AM Piotr Zarzycki wrote: > > > Hi All, > > > > I have migrated builds of Apache Royale to new server. Is there any plan > > to have more Windows machine there ? > > > > Whenever I'm running a build I need to wait 8h cause Machine is busy with > > Maven TLP etc. We didn't have so much waiting on previous jenkins. > > > > Yeah, we have 2 left on the old Jenkins for those jobs that still need > Windows over there. They will get migrated soon. > > Gav... > > > > > > Thanks, > > Piotr > > > > On 2020/07/16 16:33:08, Gavin McDonald wrote: > > > Hi All, > > > > > > This NOTICE is for everyone on builds.apache.org. We are migrating to a > > new > > > Cloudbees based Client Master called https://ci-builds.apache.org. The > > > migrations of all jobs needs to be done before the switch off date of > > 15th > > > August 2020, so you have a maximum of 4 weeks. > > > > > > There is no tool or automated way of migrating your jobs, the > > > differences in the platforms, the plugins and the setup makes it > > impossible > > > to do in a safe way. So, you all need to start creating new jobs on > > > ci-infra.a.o and then , when you are happy, turn off your old builds on > > > builds.a.o. > > > > > > There are currently 4 agents over there ready to take jobs, plus a > > floating > > > agent which is shared amongst many masters (more to come). I will migrate > > > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > > > will keep an eye of load across both and adjust accordingly. > > > > > > If needed, create a ticket on INFRA jira for any issues that crop up, or > > > email here on builds@a.o. there may be one or two plugins we need to > > > install/tweak etc. > > > > > > We will be not using 'Views' at the top level, but rather we will take > > > advantage of 'Folders Plus' - each project will get its own Folder and > > have > > > authorisation access to create/edit jobs etc within that folder. I will > > > create these folders as you ask for them to start with. This setup allows > > > for credentials isolation amongst other benefits, including but not > > limited > > > to exclusive agents (Controlled Agents) for your own use , should you > > have > > > any project targeted donations of agents. > > > > > > As with other aspects of the ASF, projects can choose to just enable all > > > committers access to their folder, just ask. > > > > > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will > > not > > > be setting up any forwarding rules or anything like that. > > > > > > So, please, get started *now *on this so you can be sure we are all > > > completed before the final cutoff date of 15th August 2020. > > > > > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > > > tickets. > > > > > > Hadoop and related projects have their own migration path to follow, same > > > cut off date, Cassandra, Beam, CouchDB have already migrated and are > > doing > > > very well in their new homes. > > > > > > Lets get going ... > > > > > > -- > > > > > > *Gavin McDonald* > > > Systems Administrator > > > ASF Infrastructure Team > > > > > > > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team >
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Piotr, On Fri, Aug 7, 2020 at 10:10 AM Piotr Zarzycki wrote: > Hi All, > > I have migrated builds of Apache Royale to new server. Is there any plan > to have more Windows machine there ? > > Whenever I'm running a build I need to wait 8h cause Machine is busy with > Maven TLP etc. We didn't have so much waiting on previous jenkins. > Yeah, we have 2 left on the old Jenkins for those jobs that still need Windows over there. They will get migrated soon. Gav... > > Thanks, > Piotr > > On 2020/07/16 16:33:08, Gavin McDonald wrote: > > Hi All, > > > > This NOTICE is for everyone on builds.apache.org. We are migrating to a > new > > Cloudbees based Client Master called https://ci-builds.apache.org. The > > migrations of all jobs needs to be done before the switch off date of > 15th > > August 2020, so you have a maximum of 4 weeks. > > > > There is no tool or automated way of migrating your jobs, the > > differences in the platforms, the plugins and the setup makes it > impossible > > to do in a safe way. So, you all need to start creating new jobs on > > ci-infra.a.o and then , when you are happy, turn off your old builds on > > builds.a.o. > > > > There are currently 4 agents over there ready to take jobs, plus a > floating > > agent which is shared amongst many masters (more to come). I will migrate > > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > > will keep an eye of load across both and adjust accordingly. > > > > If needed, create a ticket on INFRA jira for any issues that crop up, or > > email here on builds@a.o. there may be one or two plugins we need to > > install/tweak etc. > > > > We will be not using 'Views' at the top level, but rather we will take > > advantage of 'Folders Plus' - each project will get its own Folder and > have > > authorisation access to create/edit jobs etc within that folder. I will > > create these folders as you ask for them to start with. This setup allows > > for credentials isolation amongst other benefits, including but not > limited > > to exclusive agents (Controlled Agents) for your own use , should you > have > > any project targeted donations of agents. > > > > As with other aspects of the ASF, projects can choose to just enable all > > committers access to their folder, just ask. > > > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will > not > > be setting up any forwarding rules or anything like that. > > > > So, please, get started *now *on this so you can be sure we are all > > completed before the final cutoff date of 15th August 2020. > > > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > > tickets. > > > > Hadoop and related projects have their own migration path to follow, same > > cut off date, Cassandra, Beam, CouchDB have already migrated and are > doing > > very well in their new homes. > > > > Lets get going ... > > > > -- > > > > *Gavin McDonald* > > Systems Administrator > > ASF Infrastructure Team > > > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi All, I have migrated builds of Apache Royale to new server. Is there any plan to have more Windows machine there ? Whenever I'm running a build I need to wait 8h cause Machine is busy with Maven TLP etc. We didn't have so much waiting on previous jenkins. Thanks, Piotr On 2020/07/16 16:33:08, Gavin McDonald wrote: > Hi All, > > This NOTICE is for everyone on builds.apache.org. We are migrating to a new > Cloudbees based Client Master called https://ci-builds.apache.org. The > migrations of all jobs needs to be done before the switch off date of 15th > August 2020, so you have a maximum of 4 weeks. > > There is no tool or automated way of migrating your jobs, the > differences in the platforms, the plugins and the setup makes it impossible > to do in a safe way. So, you all need to start creating new jobs on > ci-infra.a.o and then , when you are happy, turn off your old builds on > builds.a.o. > > There are currently 4 agents over there ready to take jobs, plus a floating > agent which is shared amongst many masters (more to come). I will migrate > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > will keep an eye of load across both and adjust accordingly. > > If needed, create a ticket on INFRA jira for any issues that crop up, or > email here on builds@a.o. there may be one or two plugins we need to > install/tweak etc. > > We will be not using 'Views' at the top level, but rather we will take > advantage of 'Folders Plus' - each project will get its own Folder and have > authorisation access to create/edit jobs etc within that folder. I will > create these folders as you ask for them to start with. This setup allows > for credentials isolation amongst other benefits, including but not limited > to exclusive agents (Controlled Agents) for your own use , should you have > any project targeted donations of agents. > > As with other aspects of the ASF, projects can choose to just enable all > committers access to their folder, just ask. > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will not > be setting up any forwarding rules or anything like that. > > So, please, get started *now *on this so you can be sure we are all > completed before the final cutoff date of 15th August 2020. > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > tickets. > > Hadoop and related projects have their own migration path to follow, same > cut off date, Cassandra, Beam, CouchDB have already migrated and are doing > very well in their new homes. > > Lets get going ... > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team >
Re: [IMPORTANT] - Migration to ci-builds.a.o
Sorry, forgot to mention that all Kafka committers should have edit access to the folder. Ismael On Wed, Aug 5, 2020 at 8:16 PM Ismael Juma wrote: > Hi, > > Can you please create a folder for Kafka? > > Ismael > > On Thu, Jul 16, 2020 at 9:33 AM Gavin McDonald > wrote: > >> Hi All, >> >> This NOTICE is for everyone on builds.apache.org. We are migrating to a >> new >> Cloudbees based Client Master called https://ci-builds.apache.org. The >> migrations of all jobs needs to be done before the switch off date of 15th >> August 2020, so you have a maximum of 4 weeks. >> >> There is no tool or automated way of migrating your jobs, the >> differences in the platforms, the plugins and the setup makes it >> impossible >> to do in a safe way. So, you all need to start creating new jobs on >> ci-infra.a.o and then , when you are happy, turn off your old builds on >> builds.a.o. >> >> There are currently 4 agents over there ready to take jobs, plus a >> floating >> agent which is shared amongst many masters (more to come). I will migrate >> away 2 more agents from builds.a.o to ci-builds.a.o every few days, and >> will keep an eye of load across both and adjust accordingly. >> >> If needed, create a ticket on INFRA jira for any issues that crop up, or >> email here on builds@a.o. there may be one or two plugins we need to >> install/tweak etc. >> >> We will be not using 'Views' at the top level, but rather we will take >> advantage of 'Folders Plus' - each project will get its own Folder and >> have >> authorisation access to create/edit jobs etc within that folder. I will >> create these folders as you ask for them to start with. This setup allows >> for credentials isolation amongst other benefits, including but not >> limited >> to exclusive agents (Controlled Agents) for your own use , should you have >> any project targeted donations of agents. >> >> As with other aspects of the ASF, projects can choose to just enable all >> committers access to their folder, just ask. >> >> We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will not >> be setting up any forwarding rules or anything like that. >> >> So, please, get started *now *on this so you can be sure we are all >> completed before the final cutoff date of 15th August 2020. >> >> Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA >> tickets. >> >> Hadoop and related projects have their own migration path to follow, same >> cut off date, Cassandra, Beam, CouchDB have already migrated and are doing >> very well in their new homes. >> >> Lets get going ... >> >> -- >> >> *Gavin McDonald* >> Systems Administrator >> ASF Infrastructure Team >> >
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi, Can you please create a folder for Kafka? Ismael On Thu, Jul 16, 2020 at 9:33 AM Gavin McDonald wrote: > Hi All, > > This NOTICE is for everyone on builds.apache.org. We are migrating to a > new > Cloudbees based Client Master called https://ci-builds.apache.org. The > migrations of all jobs needs to be done before the switch off date of 15th > August 2020, so you have a maximum of 4 weeks. > > There is no tool or automated way of migrating your jobs, the > differences in the platforms, the plugins and the setup makes it impossible > to do in a safe way. So, you all need to start creating new jobs on > ci-infra.a.o and then , when you are happy, turn off your old builds on > builds.a.o. > > There are currently 4 agents over there ready to take jobs, plus a floating > agent which is shared amongst many masters (more to come). I will migrate > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > will keep an eye of load across both and adjust accordingly. > > If needed, create a ticket on INFRA jira for any issues that crop up, or > email here on builds@a.o. there may be one or two plugins we need to > install/tweak etc. > > We will be not using 'Views' at the top level, but rather we will take > advantage of 'Folders Plus' - each project will get its own Folder and have > authorisation access to create/edit jobs etc within that folder. I will > create these folders as you ask for them to start with. This setup allows > for credentials isolation amongst other benefits, including but not limited > to exclusive agents (Controlled Agents) for your own use , should you have > any project targeted donations of agents. > > As with other aspects of the ASF, projects can choose to just enable all > committers access to their folder, just ask. > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will not > be setting up any forwarding rules or anything like that. > > So, please, get started *now *on this so you can be sure we are all > completed before the final cutoff date of 15th August 2020. > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > tickets. > > Hadoop and related projects have their own migration path to follow, same > cut off date, Cassandra, Beam, CouchDB have already migrated and are doing > very well in their new homes. > > Lets get going ... > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team >
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Matt, On Thu, Jul 16, 2020 at 11:38 PM Matt Sicker wrote: > Couple plugin requests, though they both require a newer version of > Jenkins: > > * > https://docs.cloudbees.com/docs/cloudbees-ci/latest/slack-integration/setting-up-psm This plugin still doesnt appear for me in the list of available plugins after upgrading. > > * > https://docs.cloudbees.com/docs/cloudbees-ci/latest/scm-integration/enabling-scm-reporting This one is installed Gav... > > > On Thu, 16 Jul 2020 at 16:32, Matt Sicker wrote: > > > > Oh, I misread the initial email. Could you create a folder for Logging? > > > > On Thu, 16 Jul 2020 at 16:31, Matt Sicker wrote: > > > > > > I tried logging in, but I don't seem to have any ability to create > anything. > > > > > > On Thu, 16 Jul 2020 at 11:33, Gavin McDonald > wrote: > > > > > > > > Hi All, > > > > > > > > This NOTICE is for everyone on builds.apache.org. We are migrating > to a new > > > > Cloudbees based Client Master called https://ci-builds.apache.org. > The > > > > migrations of all jobs needs to be done before the switch off date > of 15th > > > > August 2020, so you have a maximum of 4 weeks. > > > > > > > > There is no tool or automated way of migrating your jobs, the > > > > differences in the platforms, the plugins and the setup makes it > impossible > > > > to do in a safe way. So, you all need to start creating new jobs on > > > > ci-infra.a.o and then , when you are happy, turn off your old builds > on > > > > builds.a.o. > > > > > > > > There are currently 4 agents over there ready to take jobs, plus a > floating > > > > agent which is shared amongst many masters (more to come). I will > migrate > > > > away 2 more agents from builds.a.o to ci-builds.a.o every few days, > and > > > > will keep an eye of load across both and adjust accordingly. > > > > > > > > If needed, create a ticket on INFRA jira for any issues that crop > up, or > > > > email here on builds@a.o. there may be one or two plugins we need to > > > > install/tweak etc. > > > > > > > > We will be not using 'Views' at the top level, but rather we will > take > > > > advantage of 'Folders Plus' - each project will get its own Folder > and have > > > > authorisation access to create/edit jobs etc within that folder. I > will > > > > create these folders as you ask for them to start with. This setup > allows > > > > for credentials isolation amongst other benefits, including but not > limited > > > > to exclusive agents (Controlled Agents) for your own use , should > you have > > > > any project targeted donations of agents. > > > > > > > > As with other aspects of the ASF, projects can choose to just enable > all > > > > committers access to their folder, just ask. > > > > > > > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but > will not > > > > be setting up any forwarding rules or anything like that. > > > > > > > > So, please, get started *now *on this so you can be sure we are all > > > > completed before the final cutoff date of 15th August 2020. > > > > > > > > Any questions - I expect a few (dozen :) ) - ask away and/or file > INFRA > > > > tickets. > > > > > > > > Hadoop and related projects have their own migration path to follow, > same > > > > cut off date, Cassandra, Beam, CouchDB have already migrated and are > doing > > > > very well in their new homes. > > > > > > > > Lets get going ... > > > > > > > > -- > > > > > > > > *Gavin McDonald* > > > > Systems Administrator > > > > ASF Infrastructure Team > > > > > > > > > > > > -- > > > Matt Sicker > > > > > > > > -- > > Matt Sicker > > > > -- > Matt Sicker > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Eric, On Thu, Jul 30, 2020 at 11:32 AM Eric Barboni wrote: > Hi Gavin, > > I'm not sure to get the CNAME topic. > Is the ci-builds.apache.org ok to use for badges or so ? Yes certainly, that is the new uri to use from now on. > Or we should wait and use builds.apache.org and rewrite URL to > accommodate new folders? > builds.a.o will redirect to ci-builds.a.o to allow for bookmarks/favourites/documentation etc to follow to the new uri. HTH > > Best Regards > Eric > > -Message d'origine- > De : Gavin McDonald > Envoyé : jeudi 16 juillet 2020 18:33 > À : builds > Objet : [IMPORTANT] - Migration to ci-builds.a.o > > Hi All, > > This NOTICE is for everyone on builds.apache.org. We are migrating to a > new Cloudbees based Client Master called https://ci-builds.apache.org. > The migrations of all jobs needs to be done before the switch off date of > 15th August 2020, so you have a maximum of 4 weeks. > > There is no tool or automated way of migrating your jobs, the differences > in the platforms, the plugins and the setup makes it impossible to do in a > safe way. So, you all need to start creating new jobs on ci-infra.a.o and > then , when you are happy, turn off your old builds on builds.a.o. > > There are currently 4 agents over there ready to take jobs, plus a > floating agent which is shared amongst many masters (more to come). I will > migrate away 2 more agents from builds.a.o to ci-builds.a.o every few days, > and will keep an eye of load across both and adjust accordingly. > > If needed, create a ticket on INFRA jira for any issues that crop up, or > email here on builds@a.o. there may be one or two plugins we need to > install/tweak etc. > > We will be not using 'Views' at the top level, but rather we will take > advantage of 'Folders Plus' - each project will get its own Folder and have > authorisation access to create/edit jobs etc within that folder. I will > create these folders as you ask for them to start with. This setup allows > for credentials isolation amongst other benefits, including but not limited > to exclusive agents (Controlled Agents) for your own use , should you have > any project targeted donations of agents. > > As with other aspects of the ASF, projects can choose to just enable all > committers access to their folder, just ask. > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will not > be setting up any forwarding rules or anything like that. > > So, please, get started *now *on this so you can be sure we are all > completed before the final cutoff date of 15th August 2020. > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > tickets. > > Hadoop and related projects have their own migration path to follow, same > cut off date, Cassandra, Beam, CouchDB have already migrated and are doing > very well in their new homes. > > Lets get going ... > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team > > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
RE: [IMPORTANT] - Migration to ci-builds.a.o
Hi Gavin, I'm not sure to get the CNAME topic. Is the ci-builds.apache.org ok to use for badges or so ? Or we should wait and use builds.apache.org and rewrite URL to accommodate new folders? Best Regards Eric -Message d'origine- De : Gavin McDonald Envoyé : jeudi 16 juillet 2020 18:33 À : builds Objet : [IMPORTANT] - Migration to ci-builds.a.o Hi All, This NOTICE is for everyone on builds.apache.org. We are migrating to a new Cloudbees based Client Master called https://ci-builds.apache.org. The migrations of all jobs needs to be done before the switch off date of 15th August 2020, so you have a maximum of 4 weeks. There is no tool or automated way of migrating your jobs, the differences in the platforms, the plugins and the setup makes it impossible to do in a safe way. So, you all need to start creating new jobs on ci-infra.a.o and then , when you are happy, turn off your old builds on builds.a.o. There are currently 4 agents over there ready to take jobs, plus a floating agent which is shared amongst many masters (more to come). I will migrate away 2 more agents from builds.a.o to ci-builds.a.o every few days, and will keep an eye of load across both and adjust accordingly. If needed, create a ticket on INFRA jira for any issues that crop up, or email here on builds@a.o. there may be one or two plugins we need to install/tweak etc. We will be not using 'Views' at the top level, but rather we will take advantage of 'Folders Plus' - each project will get its own Folder and have authorisation access to create/edit jobs etc within that folder. I will create these folders as you ask for them to start with. This setup allows for credentials isolation amongst other benefits, including but not limited to exclusive agents (Controlled Agents) for your own use , should you have any project targeted donations of agents. As with other aspects of the ASF, projects can choose to just enable all committers access to their folder, just ask. We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will not be setting up any forwarding rules or anything like that. So, please, get started *now *on this so you can be sure we are all completed before the final cutoff date of 15th August 2020. Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA tickets. Hadoop and related projects have their own migration path to follow, same cut off date, Cassandra, Beam, CouchDB have already migrated and are doing very well in their new homes. Lets get going ... -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Can you please create a folder for Qpid, with access for all committers. Thanks, Robbie On Thu, 16 Jul 2020 at 17:33, Gavin McDonald wrote: > > Hi All, > > This NOTICE is for everyone on builds.apache.org. We are migrating to a new > Cloudbees based Client Master called https://ci-builds.apache.org. The > migrations of all jobs needs to be done before the switch off date of 15th > August 2020, so you have a maximum of 4 weeks. > > There is no tool or automated way of migrating your jobs, the > differences in the platforms, the plugins and the setup makes it impossible > to do in a safe way. So, you all need to start creating new jobs on > ci-infra.a.o and then , when you are happy, turn off your old builds on > builds.a.o. > > There are currently 4 agents over there ready to take jobs, plus a floating > agent which is shared amongst many masters (more to come). I will migrate > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > will keep an eye of load across both and adjust accordingly. > > If needed, create a ticket on INFRA jira for any issues that crop up, or > email here on builds@a.o. there may be one or two plugins we need to > install/tweak etc. > > We will be not using 'Views' at the top level, but rather we will take > advantage of 'Folders Plus' - each project will get its own Folder and have > authorisation access to create/edit jobs etc within that folder. I will > create these folders as you ask for them to start with. This setup allows > for credentials isolation amongst other benefits, including but not limited > to exclusive agents (Controlled Agents) for your own use , should you have > any project targeted donations of agents. > > As with other aspects of the ASF, projects can choose to just enable all > committers access to their folder, just ask. > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will not > be setting up any forwarding rules or anything like that. > > So, please, get started *now *on this so you can be sure we are all > completed before the final cutoff date of 15th August 2020. > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > tickets. > > Hadoop and related projects have their own migration path to follow, same > cut off date, Cassandra, Beam, CouchDB have already migrated and are doing > very well in their new homes. > > Lets get going ... > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
I just tried the 'git-websites' label for Groovy. Worked without a glitch: https://ci-builds.apache.org/job/Groovy/job/Groovy%20dev%20website/1/ but about half the speed of before: https://builds.apache.org/view/E-G/view/Groovy/job/Groovy%20dev%20website/130/ Is that to be expected? It's not impacting us for this particular build but good to know in terms of expectations when we convert over some of the other builds. Cheers, Paul. On Wed, Jul 22, 2020 at 6:17 AM Roy Lenferink wrote: > The new build environment uses a so called ‘floating agent’ for deploying > websites. It is shared over different masters (ci-builds being one of them) > and will become available when using the ‘git-websites’ label. > > I already tested this for Celix and it works. > > See for examples: > - https://ci-builds.apache.org/job/Celix/job/site/job/master/4/console > - https://github.com/apache/celix-site/blob/master/Jenkinsfile#L22 > > Op di 21 jul. 2020 om 22:09 schreef Zoran Regvart > > > On Tue, Jul 21, 2020 at 9:40 PM Eugen Stan > wrote: > > > I'm pushing to staging. > > > It should work for live I guess. > > > Have you tried and failed? > > > > > > > > > https://ci-builds.apache.org/job/james/job/ApacheJames-Website/job/live/3/console > > > > I did not, I was wondering if website nodes were missing so I would > > hold off until those were online. That build ran on ubuntu node, which > > on builds.a.o did not have the necessary credentials to push to git. > > > > zoran > > -- > > Zoran Regvart > > >
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Eric. On Wed, Jul 22, 2020 at 1:17 PM Eric Barboni wrote: > Hi, > As there is a folder per TLP project, can we use view feature ? Or we > should still avoid that. > If you want to use Views 'within' your folder, that's fine , just don't want cluttered up views outside of those HTH Gav... Best Regards > Eric > > > -Message d'origine- > De : Roy Lenferink > Envoyé : mardi 21 juillet 2020 22:17 > À : builds@apache.org > Objet : Re: [IMPORTANT] - Migration to ci-builds.a.o > > The new build environment uses a so called ‘floating agent’ for deploying > websites. It is shared over different masters (ci-builds being one of them) > and will become available when using the ‘git-websites’ label. > > I already tested this for Celix and it works. > > See for examples: > - https://ci-builds.apache.org/job/Celix/job/site/job/master/4/console > - https://github.com/apache/celix-site/blob/master/Jenkinsfile#L22 > > Op di 21 jul. 2020 om 22:09 schreef Zoran Regvart > > > On Tue, Jul 21, 2020 at 9:40 PM Eugen Stan > wrote: > > > I'm pushing to staging. > > > It should work for live I guess. > > > Have you tried and failed? > > > > > > > > https://ci-builds.apache.org/job/james/job/ApacheJames-Website/job/liv > > e/3/console > > > > I did not, I was wondering if website nodes were missing so I would > > hold off until those were online. That build ran on ubuntu node, which > > on builds.a.o did not have the necessary credentials to push to git. > > > > zoran > > -- > > Zoran Regvart > > > > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
RE: [IMPORTANT] - Migration to ci-builds.a.o
Hi, As there is a folder per TLP project, can we use view feature ? Or we should still avoid that. Best Regards Eric -Message d'origine- De : Roy Lenferink Envoyé : mardi 21 juillet 2020 22:17 À : builds@apache.org Objet : Re: [IMPORTANT] - Migration to ci-builds.a.o The new build environment uses a so called ‘floating agent’ for deploying websites. It is shared over different masters (ci-builds being one of them) and will become available when using the ‘git-websites’ label. I already tested this for Celix and it works. See for examples: - https://ci-builds.apache.org/job/Celix/job/site/job/master/4/console - https://github.com/apache/celix-site/blob/master/Jenkinsfile#L22 Op di 21 jul. 2020 om 22:09 schreef Zoran Regvart > On Tue, Jul 21, 2020 at 9:40 PM Eugen Stan wrote: > > I'm pushing to staging. > > It should work for live I guess. > > Have you tried and failed? > > > > > https://ci-builds.apache.org/job/james/job/ApacheJames-Website/job/liv > e/3/console > > I did not, I was wondering if website nodes were missing so I would > hold off until those were online. That build ran on ubuntu node, which > on builds.a.o did not have the necessary credentials to push to git. > > zoran > -- > Zoran Regvart >
Re: [IMPORTANT] - Migration to ci-builds.a.o
The new build environment uses a so called ‘floating agent’ for deploying websites. It is shared over different masters (ci-builds being one of them) and will become available when using the ‘git-websites’ label. I already tested this for Celix and it works. See for examples: - https://ci-builds.apache.org/job/Celix/job/site/job/master/4/console - https://github.com/apache/celix-site/blob/master/Jenkinsfile#L22 Op di 21 jul. 2020 om 22:09 schreef Zoran Regvart > On Tue, Jul 21, 2020 at 9:40 PM Eugen Stan wrote: > > I'm pushing to staging. > > It should work for live I guess. > > Have you tried and failed? > > > > > https://ci-builds.apache.org/job/james/job/ApacheJames-Website/job/live/3/console > > I did not, I was wondering if website nodes were missing so I would > hold off until those were online. That build ran on ubuntu node, which > on builds.a.o did not have the necessary credentials to push to git. > > zoran > -- > Zoran Regvart >
Re: [IMPORTANT] - Migration to ci-builds.a.o
La 21.07.2020 23:08, Zoran Regvart a scris:
On Tue, Jul 21, 2020 at 9:40 PM Eugen Stan wrote:
I'm pushing to staging.
It should work for live I guess.
Have you tried and failed?
https://ci-builds.apache.org/job/james/job/ApacheJames-Website/job/live/3/console
I did not, I was wondering if website nodes were missing so I would
hold off until those were online. That build ran on ubuntu node, which
on builds.a.o did not have the necessary credentials to push to git.
zoran
It's running on git-websites
https://github.com/apache/james-site/blob/live/Jenkinsfile#L65
stage('Publish') {
agent {
node {
label 'git-websites'
}
}
}
--
Eugen Stan
+40720 898 747 / netdava.com
Re: [IMPORTANT] - Migration to ci-builds.a.o
On Tue, Jul 21, 2020 at 9:40 PM Eugen Stan wrote: > I'm pushing to staging. > It should work for live I guess. > Have you tried and failed? > > https://ci-builds.apache.org/job/james/job/ApacheJames-Website/job/live/3/console I did not, I was wondering if website nodes were missing so I would hold off until those were online. That build ran on ubuntu node, which on builds.a.o did not have the necessary credentials to push to git. zoran -- Zoran Regvart
Re: [IMPORTANT] - Migration to ci-builds.a.o
La 21.07.2020 22:31, Zoran Regvart a scris: Hi Gavin, can websites with the current ability to push to asf-site branch be built on the new infrastructure? zoran I'm pushing to staging. It should work for live I guess. Have you tried and failed? https://ci-builds.apache.org/job/james/job/ApacheJames-Website/job/live/3/console -- Eugen Stan +40720 898 747 / netdava.com
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Gavin, can websites with the current ability to push to asf-site branch be built on the new infrastructure? zoran On Thu, Jul 16, 2020 at 6:33 PM Gavin McDonald wrote: > > Hi All, > > This NOTICE is for everyone on builds.apache.org. We are migrating to a new > Cloudbees based Client Master called https://ci-builds.apache.org. The > migrations of all jobs needs to be done before the switch off date of 15th > August 2020, so you have a maximum of 4 weeks. > > There is no tool or automated way of migrating your jobs, the > differences in the platforms, the plugins and the setup makes it impossible > to do in a safe way. So, you all need to start creating new jobs on > ci-infra.a.o and then , when you are happy, turn off your old builds on > builds.a.o. > > There are currently 4 agents over there ready to take jobs, plus a floating > agent which is shared amongst many masters (more to come). I will migrate > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > will keep an eye of load across both and adjust accordingly. > > If needed, create a ticket on INFRA jira for any issues that crop up, or > email here on builds@a.o. there may be one or two plugins we need to > install/tweak etc. > > We will be not using 'Views' at the top level, but rather we will take > advantage of 'Folders Plus' - each project will get its own Folder and have > authorisation access to create/edit jobs etc within that folder. I will > create these folders as you ask for them to start with. This setup allows > for credentials isolation amongst other benefits, including but not limited > to exclusive agents (Controlled Agents) for your own use , should you have > any project targeted donations of agents. > > As with other aspects of the ASF, projects can choose to just enable all > committers access to their folder, just ask. > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will not > be setting up any forwarding rules or anything like that. > > So, please, get started *now *on this so you can be sure we are all > completed before the final cutoff date of 15th August 2020. > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > tickets. > > Hadoop and related projects have their own migration path to follow, same > cut off date, Cassandra, Beam, CouchDB have already migrated and are doing > very well in their new homes. > > Lets get going ... > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team -- Zoran Regvart
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Gavin, can you create a folder for Sling with edit rights for all Sling committers?
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Gav, I just had the impression that Creadur builds spent quite a long time in the queue, but the build went through after a while Sorry for the noise, Phil Am 19.07.20 um 23:34 schrieb Gavin McDonald: > hm, I'd like to know more about what is happening here, what do you mean > by 'speed up build time' ? My wild guess is that by not limiting the pool > of > available exexutors by choosing a label means a shorter build time? Not > really, it may make grab an executor quicker if the conditions are right, > but > actual build time on an agent after that should be the same.
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Phil, On Sun, Jul 19, 2020 at 9:32 PM P. Ottlinger wrote: > Hi Gav, > > Am 17.07.20 um 21:56 schrieb Gavin McDonald: > >> can you create a Creadur as well with the right to create jobs for all > >> PMC-members? > >> > > > > Done, but I extended the scope slightly to all Creadur Committers - I > dont > > see > > why this should just be PMC Members creating Jenkins jobs, please do let > > me know if I did the wrong thing there. > > Everything is fine, thanks. > > All older Creadur-jobs had the label to only run on "ubuntu" nodes - in > order to ease the setup I tried to not restrict where builds are > running, but this doesn't seem to speed up build time. > hm, I'd like to know more about what is happening here, what do you mean by 'speed up build time' ? My wild guess is that by not limiting the pool of available exexutors by choosing a label means a shorter build time? Not really, it may make grab an executor quicker if the conditions are right, but actual build time on an agent after that should be the same. > > Should I add "ubuntu" to node restrictions or is the new Jenkins just > lacking build nodes? > Unless your build works on Windows then I would choose the 'ubuntu' label. 99% of all agents on the new ci-builds.a.o will be 'ubuntu' Currently we have 4 agents totalling 8 executors, and I haven't see any build up of a queue yet, mostly they have been pretty much idle so lack of build agents/nodes is not an issue currently. HTH > > Thanks, > Phil > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Gav, Am 17.07.20 um 21:56 schrieb Gavin McDonald: >> can you create a Creadur as well with the right to create jobs for all >> PMC-members? >> > > Done, but I extended the scope slightly to all Creadur Committers - I dont > see > why this should just be PMC Members creating Jenkins jobs, please do let > me know if I did the wrong thing there. Everything is fine, thanks. All older Creadur-jobs had the label to only run on "ubuntu" nodes - in order to ease the setup I tried to not restrict where builds are running, but this doesn't seem to speed up build time. Should I add "ubuntu" to node restrictions or is the new Jenkins just lacking build nodes? Thanks, Phil
Re: [IMPORTANT] - Migration to ci-builds.a.o
I think these days Maxim you login to Sonarcloud.io with your github creds and create a personal token On Sat, Jul 18, 2020 at 1:36 PM Maxim Solodovnik wrote: > The only credentials I can see in drop-down is GitHub PR Builder asf-ci > Token > no Sonar token :(( > > On Sat, 18 Jul 2020 at 16:51, Gavin McDonald wrote: > >> Hi Maxim, >> >> On Sat, Jul 18, 2020 at 3:24 AM Maxim Solodovnik >> wrote: >> >>> Hello Gavin, >>> >>> It seems sonar integration is missing (Credentials dropdown for sonar is >>> missing) >>> >> >> Try again please. >> >>> >>> -- >>> Best regards, >>> Maxim >>> >> >> >> -- >> *Gavin McDonald* >> Systems Administrator >> ASF Infrastructure Team >> >> > > -- > Best regards, > Maxim > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Chris, On Sun, Jul 19, 2020 at 2:02 PM Christofer Dutz wrote: > Another question. > > As I was asked to setup and check plc4x-vm2.apache.org ... could this be > simply be setup as PLC4X' build agent for ci-builds.apache.org? > I think then I'll be really able to setup things correctly and then we can > just turn off the old. > Please create a new INFRA ticket to have this VM set up as a dedicated agent for the plc4x project > > Chris > > > > Am 19.07.20, 13:17 schrieb "Christofer Dutz" : > > Hi, > > could you please create the folder for the Apache PLC4X project? > > Thanks, > > Chris > > Am 18.07.20, 20:04 schrieb "Stefan Seelmann" >: > > Done: https://issues.apache.org/jira/browse/INFRA-20545 > > On 7/18/20 7:25 PM, Gavin McDonald wrote: > > Thanks Stefan, > > > > Can you create an INFRA jira ticket for this one please. > > > > On Sat, Jul 18, 2020 at 5:48 PM Stefan Seelmann < > m...@stefan-seelmann.de> > > wrote: > > > >> On 7/17/20 8:41 PM, Gavin McDonald wrote: > Right now there seem to be no executors running Windows or am > I > overlooking something? I assume they will be added later. > > >>> > >>> There are 2 configured as 'floating agents' meaning they are > available > >> for > >>> ci-builds and > >>> all the other project specific masters we have. Use the > 'Windows' label. > >> > >> I tried to use the in two jobs [1],[2] however it doesn't work. > >> > >> In https://jenkins-ccos.apache.org/ I see > jenkins-win-he-de-5|6, when > >> starting a job the state of the nodes changes to " Node on > lease to > >> Masters » Builds » ci-builds.apache.org (on-line) for XY sec", > but the > >> job never starts and the node also doesn't show up in the > executors > >> list. After about one minute the status changes back to "Node > returned > >> from lease" to "Node being de-provisioned" to "Available for > lease" again. > >> > >> Kind Regards, > >> Stefan > >> > >> [1] > https://ci-builds.apache.org/job/Directory/job/dir-test-windows/ > >> [2] > https://ci-builds.apache.org/job/Directory/job/dir-ldap-api-pipeline/ > >> > > > > > > > > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Another question. As I was asked to setup and check plc4x-vm2.apache.org ... could this be simply be setup as PLC4X' build agent for ci-builds.apache.org? I think then I'll be really able to setup things correctly and then we can just turn off the old. Chris Am 19.07.20, 13:17 schrieb "Christofer Dutz" : Hi, could you please create the folder for the Apache PLC4X project? Thanks, Chris Am 18.07.20, 20:04 schrieb "Stefan Seelmann" : Done: https://issues.apache.org/jira/browse/INFRA-20545 On 7/18/20 7:25 PM, Gavin McDonald wrote: > Thanks Stefan, > > Can you create an INFRA jira ticket for this one please. > > On Sat, Jul 18, 2020 at 5:48 PM Stefan Seelmann > wrote: > >> On 7/17/20 8:41 PM, Gavin McDonald wrote: Right now there seem to be no executors running Windows or am I overlooking something? I assume they will be added later. >>> >>> There are 2 configured as 'floating agents' meaning they are available >> for >>> ci-builds and >>> all the other project specific masters we have. Use the 'Windows' label. >> >> I tried to use the in two jobs [1],[2] however it doesn't work. >> >> In https://jenkins-ccos.apache.org/ I see jenkins-win-he-de-5|6, when >> starting a job the state of the nodes changes to " Node on lease to >> Masters » Builds » ci-builds.apache.org (on-line) for XY sec", but the >> job never starts and the node also doesn't show up in the executors >> list. After about one minute the status changes back to "Node returned >> from lease" to "Node being de-provisioned" to "Available for lease" again. >> >> Kind Regards, >> Stefan >> >> [1] https://ci-builds.apache.org/job/Directory/job/dir-test-windows/ >> [2] https://ci-builds.apache.org/job/Directory/job/dir-ldap-api-pipeline/ >> > >
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi, could you please create the folder for the Apache PLC4X project? Thanks, Chris Am 18.07.20, 20:04 schrieb "Stefan Seelmann" : Done: https://issues.apache.org/jira/browse/INFRA-20545 On 7/18/20 7:25 PM, Gavin McDonald wrote: > Thanks Stefan, > > Can you create an INFRA jira ticket for this one please. > > On Sat, Jul 18, 2020 at 5:48 PM Stefan Seelmann > wrote: > >> On 7/17/20 8:41 PM, Gavin McDonald wrote: Right now there seem to be no executors running Windows or am I overlooking something? I assume they will be added later. >>> >>> There are 2 configured as 'floating agents' meaning they are available >> for >>> ci-builds and >>> all the other project specific masters we have. Use the 'Windows' label. >> >> I tried to use the in two jobs [1],[2] however it doesn't work. >> >> In https://jenkins-ccos.apache.org/ I see jenkins-win-he-de-5|6, when >> starting a job the state of the nodes changes to " Node on lease to >> Masters » Builds » ci-builds.apache.org (on-line) for XY sec", but the >> job never starts and the node also doesn't show up in the executors >> list. After about one minute the status changes back to "Node returned >> from lease" to "Node being de-provisioned" to "Available for lease" again. >> >> Kind Regards, >> Stefan >> >> [1] https://ci-builds.apache.org/job/Directory/job/dir-test-windows/ >> [2] https://ci-builds.apache.org/job/Directory/job/dir-ldap-api-pipeline/ >> > >
Re: [IMPORTANT] - Migration to ci-builds.a.o
Done: https://issues.apache.org/jira/browse/INFRA-20545 On 7/18/20 7:25 PM, Gavin McDonald wrote: > Thanks Stefan, > > Can you create an INFRA jira ticket for this one please. > > On Sat, Jul 18, 2020 at 5:48 PM Stefan Seelmann > wrote: > >> On 7/17/20 8:41 PM, Gavin McDonald wrote: Right now there seem to be no executors running Windows or am I overlooking something? I assume they will be added later. >>> >>> There are 2 configured as 'floating agents' meaning they are available >> for >>> ci-builds and >>> all the other project specific masters we have. Use the 'Windows' label. >> >> I tried to use the in two jobs [1],[2] however it doesn't work. >> >> In https://jenkins-ccos.apache.org/ I see jenkins-win-he-de-5|6, when >> starting a job the state of the nodes changes to " Node on lease to >> Masters » Builds » ci-builds.apache.org (on-line) for XY sec", but the >> job never starts and the node also doesn't show up in the executors >> list. After about one minute the status changes back to "Node returned >> from lease" to "Node being de-provisioned" to "Available for lease" again. >> >> Kind Regards, >> Stefan >> >> [1] https://ci-builds.apache.org/job/Directory/job/dir-test-windows/ >> [2] https://ci-builds.apache.org/job/Directory/job/dir-ldap-api-pipeline/ >> > >
Re: [IMPORTANT] - Migration to ci-builds.a.o
Thanks Stefan, Can you create an INFRA jira ticket for this one please. On Sat, Jul 18, 2020 at 5:48 PM Stefan Seelmann wrote: > On 7/17/20 8:41 PM, Gavin McDonald wrote: > >> Right now there seem to be no executors running Windows or am I > >> overlooking something? I assume they will be added later. > >> > > > > There are 2 configured as 'floating agents' meaning they are available > for > > ci-builds and > > all the other project specific masters we have. Use the 'Windows' label. > > I tried to use the in two jobs [1],[2] however it doesn't work. > > In https://jenkins-ccos.apache.org/ I see jenkins-win-he-de-5|6, when > starting a job the state of the nodes changes to " Node on lease to > Masters » Builds » ci-builds.apache.org (on-line) for XY sec", but the > job never starts and the node also doesn't show up in the executors > list. After about one minute the status changes back to "Node returned > from lease" to "Node being de-provisioned" to "Available for lease" again. > > Kind Regards, > Stefan > > [1] https://ci-builds.apache.org/job/Directory/job/dir-test-windows/ > [2] https://ci-builds.apache.org/job/Directory/job/dir-ldap-api-pipeline/ > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
On 7/17/20 8:41 PM, Gavin McDonald wrote: >> Right now there seem to be no executors running Windows or am I >> overlooking something? I assume they will be added later. >> > > There are 2 configured as 'floating agents' meaning they are available for > ci-builds and > all the other project specific masters we have. Use the 'Windows' label. I tried to use the in two jobs [1],[2] however it doesn't work. In https://jenkins-ccos.apache.org/ I see jenkins-win-he-de-5|6, when starting a job the state of the nodes changes to " Node on lease to Masters » Builds » ci-builds.apache.org (on-line) for XY sec", but the job never starts and the node also doesn't show up in the executors list. After about one minute the status changes back to "Node returned from lease" to "Node being de-provisioned" to "Available for lease" again. Kind Regards, Stefan [1] https://ci-builds.apache.org/job/Directory/job/dir-test-windows/ [2] https://ci-builds.apache.org/job/Directory/job/dir-ldap-api-pipeline/
Re: [IMPORTANT] - Migration to ci-builds.a.o
Yes, that one. Otherwise, I don’t think we’ll get push based build triggers on gitbox URLs. On Sat, Jul 18, 2020 at 04:47 Gavin McDonald wrote: > Hi Matt > > On Sat, Jul 18, 2020 at 1:57 AM Matt Sicker wrote: > >> One other plugin that might be missing: the gitbox SCM source? Not sure >> how to configure webhooks otherwise without creating a personal API token >> on GitHub or something. >> > > Are we talking about the asf-gitpubsub plugin here (from Stephen Connelly)? > > >> > One other plugin I noticed I was using is Warnings NG: > https://plugins.jenkins.io/warnings-ng/ > Installed > > -- > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team > > -- Matt Sicker
Re: [IMPORTANT] - Migration to ci-builds.a.o
The only credentials I can see in drop-down is GitHub PR Builder asf-ci Token no Sonar token :(( On Sat, 18 Jul 2020 at 16:51, Gavin McDonald wrote: > Hi Maxim, > > On Sat, Jul 18, 2020 at 3:24 AM Maxim Solodovnik > wrote: > >> Hello Gavin, >> >> It seems sonar integration is missing (Credentials dropdown for sonar is >> missing) >> > > Try again please. > >> >> -- >> Best regards, >> Maxim >> > > > -- > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team > > -- Best regards, Maxim
Re: [IMPORTANT] - Migration to ci-builds.a.o
Thanks a lot! W dniu sob., 18.07.2020 o 12:03 Gavin McDonald napisał(a): > Hi Andreas > > On Sat, Jul 18, 2020 at 11:54 AM Andreas Lehmkuehler > wrote: > > > Hi, > > > > I can't create new jobs for PDFBox due to the missing svn integration. > > > > Thanks, installed and will be active after the pending restart. > > > > > > > > Please add the missing plugin, I guess > > https://plugins.jenkins.io/subversion/ > > > > Thanks > > Andreas > > > > > > Am 16.07.20 um 18:33 schrieb Gavin McDonald: > > > Hi All, > > > > > > This NOTICE is for everyone on builds.apache.org. We are migrating to > a > > new > > > Cloudbees based Client Master called https://ci-builds.apache.org. The > > > migrations of all jobs needs to be done before the switch off date of > > 15th > > > August 2020, so you have a maximum of 4 weeks. > > > > > > There is no tool or automated way of migrating your jobs, the > > > differences in the platforms, the plugins and the setup makes it > > impossible > > > to do in a safe way. So, you all need to start creating new jobs on > > > ci-infra.a.o and then , when you are happy, turn off your old builds on > > > builds.a.o. > > > > > > There are currently 4 agents over there ready to take jobs, plus a > > floating > > > agent which is shared amongst many masters (more to come). I will > migrate > > > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > > > will keep an eye of load across both and adjust accordingly. > > > > > > If needed, create a ticket on INFRA jira for any issues that crop up, > or > > > email here on builds@a.o. there may be one or two plugins we need to > > > install/tweak etc. > > > > > > We will be not using 'Views' at the top level, but rather we will take > > > advantage of 'Folders Plus' - each project will get its own Folder and > > have > > > authorisation access to create/edit jobs etc within that folder. I will > > > create these folders as you ask for them to start with. This setup > allows > > > for credentials isolation amongst other benefits, including but not > > limited > > > to exclusive agents (Controlled Agents) for your own use , should you > > have > > > any project targeted donations of agents. > > > > > > As with other aspects of the ASF, projects can choose to just enable > all > > > committers access to their folder, just ask. > > > > > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will > > not > > > be setting up any forwarding rules or anything like that. > > > > > > So, please, get started *now *on this so you can be sure we are all > > > completed before the final cutoff date of 15th August 2020. > > > > > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > > > tickets. > > > > > > Hadoop and related projects have their own migration path to follow, > same > > > cut off date, Cassandra, Beam, CouchDB have already migrated and are > > doing > > > very well in their new homes. > > > > > > Lets get going ... > > > > > > > > > -- > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team > -- (mobile)
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Andreas On Sat, Jul 18, 2020 at 11:54 AM Andreas Lehmkuehler wrote: > Hi, > > I can't create new jobs for PDFBox due to the missing svn integration. > Thanks, installed and will be active after the pending restart. > > > Please add the missing plugin, I guess > https://plugins.jenkins.io/subversion/ > > Thanks > Andreas > > > Am 16.07.20 um 18:33 schrieb Gavin McDonald: > > Hi All, > > > > This NOTICE is for everyone on builds.apache.org. We are migrating to a > new > > Cloudbees based Client Master called https://ci-builds.apache.org. The > > migrations of all jobs needs to be done before the switch off date of > 15th > > August 2020, so you have a maximum of 4 weeks. > > > > There is no tool or automated way of migrating your jobs, the > > differences in the platforms, the plugins and the setup makes it > impossible > > to do in a safe way. So, you all need to start creating new jobs on > > ci-infra.a.o and then , when you are happy, turn off your old builds on > > builds.a.o. > > > > There are currently 4 agents over there ready to take jobs, plus a > floating > > agent which is shared amongst many masters (more to come). I will migrate > > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > > will keep an eye of load across both and adjust accordingly. > > > > If needed, create a ticket on INFRA jira for any issues that crop up, or > > email here on builds@a.o. there may be one or two plugins we need to > > install/tweak etc. > > > > We will be not using 'Views' at the top level, but rather we will take > > advantage of 'Folders Plus' - each project will get its own Folder and > have > > authorisation access to create/edit jobs etc within that folder. I will > > create these folders as you ask for them to start with. This setup allows > > for credentials isolation amongst other benefits, including but not > limited > > to exclusive agents (Controlled Agents) for your own use , should you > have > > any project targeted donations of agents. > > > > As with other aspects of the ASF, projects can choose to just enable all > > committers access to their folder, just ask. > > > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will > not > > be setting up any forwarding rules or anything like that. > > > > So, please, get started *now *on this so you can be sure we are all > > completed before the final cutoff date of 15th August 2020. > > > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > > tickets. > > > > Hadoop and related projects have their own migration path to follow, same > > cut off date, Cassandra, Beam, CouchDB have already migrated and are > doing > > very well in their new homes. > > > > Lets get going ... > > > > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi, I can't create new jobs for PDFBox due to the missing svn integration. Please add the missing plugin, I guess https://plugins.jenkins.io/subversion/ Thanks Andreas Am 16.07.20 um 18:33 schrieb Gavin McDonald: Hi All, This NOTICE is for everyone on builds.apache.org. We are migrating to a new Cloudbees based Client Master called https://ci-builds.apache.org. The migrations of all jobs needs to be done before the switch off date of 15th August 2020, so you have a maximum of 4 weeks. There is no tool or automated way of migrating your jobs, the differences in the platforms, the plugins and the setup makes it impossible to do in a safe way. So, you all need to start creating new jobs on ci-infra.a.o and then , when you are happy, turn off your old builds on builds.a.o. There are currently 4 agents over there ready to take jobs, plus a floating agent which is shared amongst many masters (more to come). I will migrate away 2 more agents from builds.a.o to ci-builds.a.o every few days, and will keep an eye of load across both and adjust accordingly. If needed, create a ticket on INFRA jira for any issues that crop up, or email here on builds@a.o. there may be one or two plugins we need to install/tweak etc. We will be not using 'Views' at the top level, but rather we will take advantage of 'Folders Plus' - each project will get its own Folder and have authorisation access to create/edit jobs etc within that folder. I will create these folders as you ask for them to start with. This setup allows for credentials isolation amongst other benefits, including but not limited to exclusive agents (Controlled Agents) for your own use , should you have any project targeted donations of agents. As with other aspects of the ASF, projects can choose to just enable all committers access to their folder, just ask. We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will not be setting up any forwarding rules or anything like that. So, please, get started *now *on this so you can be sure we are all completed before the final cutoff date of 15th August 2020. Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA tickets. Hadoop and related projects have their own migration path to follow, same cut off date, Cassandra, Beam, CouchDB have already migrated and are doing very well in their new homes. Lets get going ...
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Maxim, On Sat, Jul 18, 2020 at 3:24 AM Maxim Solodovnik wrote: > Hello Gavin, > > It seems sonar integration is missing (Credentials dropdown for sonar is > missing) > Try again please. > > -- > Best regards, > Maxim > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Matt On Sat, Jul 18, 2020 at 1:57 AM Matt Sicker wrote: > One other plugin that might be missing: the gitbox SCM source? Not sure > how to configure webhooks otherwise without creating a personal API token > on GitHub or something. > Are we talking about the asf-gitpubsub plugin here (from Stephen Connelly)? > >>> One other plugin I noticed I was using is Warnings NG: https://plugins.jenkins.io/warnings-ng/ >>> >>> Installed -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Maxim On Sat, Jul 18, 2020 at 3:55 AM Maxim Solodovnik wrote: > PR builds also seems to be not enabled > File an INFRA jira ticket please, with much more details, not enabled how and where etc. > >> >>> >> 3 months is about the best we can do and any releases of Jenkins in >>> >> between >>> >> those times will just have to wait until our next upgrade cycle. >>> >> >>> >> >>> >>> One other plugin I noticed I was using is Warnings NG: >>> >>> https://plugins.jenkins.io/warnings-ng/ >>> >>> >>> >>> On Fri, 17 Jul 2020 at 17:53, Gavin McDonald >>> >>> wrote: >>> >>> > >>> >>> > Hi Matt >>> >>> > >>> >>> > On Sat, Jul 18, 2020 at 12:35 AM Matt Sicker >>> wrote: >>> >>> >> >>> >>> >> Could you add the Slack plugin? https://plugins.jenkins.io/slack/ >>> >>> >> >>> >>> > >>> >>> > interestingly, that one does not appear on the list of available >>> >>> plugins. >>> >>> > >>> >>> > I'll check into it. >>> >>> > >>> >>> > >>> >>> >> >>> >>> >> On Fri, 17 Jul 2020 at 17:27, Gavin McDonald < >>> gmcdon...@apache.org> >>> >>> wrote: >>> >>> >> > >>> >>> >> > Hi Sebb >>> >>> >> > >>> >>> >> > On Fri, Jul 17, 2020 at 11:27 PM sebb wrote: >>> >>> >> > >>> >>> >> > > Also email is not working >>> >>> >> > > >>> >>> >> > > ERROR: Could not connect to SMTP host: localhost, port: 25 >>> >>> >> > > javax.mail.MessagingException: Could not connect to SMTP host: >>> >>> localhost, port: 25; >>> >>> >> > > nested exception is: >>> >>> >> > > java.net.ConnectException: Connection refused >>> (Connection >>> >>> refused) >>> >>> >> > > >>> >>> >> > > >>> >>> >> > Try again please. >>> >>> >> > >>> >>> >> > >>> >>> >> > > >>> >>> >> > > >>> >>> >> > > On Fri, 17 Jul 2020 at 22:24, Gavin McDonald < >>> >>> gmcdon...@apache.org> wrote: >>> >>> >> > > >>> >>> >> > >> Hi Sebb, >>> >>> >> > >> >>> >>> >> > >> On Fri, Jul 17, 2020 at 11:04 PM sebb >>> wrote: >>> >>> >> > >> >>> >>> >> > >>> >>> >>> >> > >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald < >>> >>> gmcdon...@apache.org> >>> >>> >> > >>> wrote: >>> >>> >> > >>> >>> >>> >> > Hi Sebb >>> >>> >> > >>> >>> >> > On Fri, Jul 17, 2020 at 2:10 PM sebb >>> wrote: >>> >>> >> > >>> >>> >> > > Please create Commons >>> >>> >> > > >>> >>> >> > >>> >>> >> > Added ,please test. >>> >>> >> > >>> >>> >> > >>> >>> >> > >>> Thanks. >>> >>> >> > >>> >>> >>> >> > >>> Build Pre Steps does not support "Inject Environment >>> Variables" >>> >>> >> > >>> >>> >>> >> > >>> There are far fewer possible types of Pre Step. >>> >>> >> > >>> Maybe there are others that are missing; I've only looked at >>> >>> one job so >>> >>> >> > >>> far. >>> >>> >> > >>> >>> >>> >> > >> >>> >>> >> > >> Thanks, please file an INFRA jira >>> >>> >> > >> >>> >>> >> > >> >>> >>> >> > >>> >>> >>> >> > >>> >>> >>> >> > -- >>> >>> >> > >>> >>> >> > *Gavin McDonald* >>> >>> >> > Systems Administrator >>> >>> >> > ASF Infrastructure Team >>> >>> >> > >>> >>> >> > >>> >>> >>> >> > >> >>> >>> >> > >> -- >>> >>> >> > >> >>> >>> >> > >> *Gavin McDonald* >>> >>> >> > >> Systems Administrator >>> >>> >> > >> ASF Infrastructure Team >>> >>> >> > >> >>> >>> >> > > >>> >>> >> > >>> >>> >> > -- >>> >>> >> > >>> >>> >> > *Gavin McDonald* >>> >>> >> > Systems Administrator >>> >>> >> > ASF Infrastructure Team >>> >>> >> >>> >>> >> >>> >>> >> >>> >>> >> -- >>> >>> >> Matt Sicker >>> >>> > >>> >>> > >>> >>> > >>> >>> > -- >>> >>> > Gavin McDonald >>> >>> > Systems Administrator >>> >>> > ASF Infrastructure Team >>> >>> > >>> >>> >>> >>> >>> >>> -- >>> >>> Matt Sicker >>> >>> >>> >> >>> >> >>> >> -- >>> >> *Gavin McDonald* >>> >> Systems Administrator >>> >> ASF Infrastructure Team >>> >> >>> >> >>> > >>> > -- >>> > Matt Sicker >>> > >>> >>> >>> -- >>> Matt Sicker >>> >> >> >> -- >> Best regards, >> Maxim >> > > > -- > Best regards, > Maxim > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Mike, On Sat, Jul 18, 2020 at 12:50 AM Mike Jumper wrote: > Hi Gavin, > > Could you please create a folder for Guacamole, with access granted to all > Guacamole committers? > All done. > > Thanks, > > - Mike > >> >> -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Olivier, On Sat, Jul 18, 2020 at 7:59 AM Olivier Lamy wrote: > Hi > Yes please this one. > @Gav can you please create folders for Maven Done > and Archiva? > Already done :) > Thanks > Olivier > > On Sat, 18 Jul 2020 at 09:57, Matt Sicker wrote: > > > One other plugin that might be missing: the gitbox SCM source? Not sure > how > > to configure webhooks otherwise without creating a personal API token on > > GitHub or something. > > > > On Fri, 17 Jul 2020 at 18:10, Matt Sicker wrote: > > > > > That's fine with me. The Slack plugin isn't too big a deal since > there's > > a > > > different one available after updating Core in the first place. The > > > Warnings NG plugin would be great to get reinstalled, though. > > > > > > On Fri, 17 Jul 2020 at 18:06, Gavin McDonald > > wrote: > > > > > >> Hi Matt > > >> > > >> On Sat, Jul 18, 2020 at 12:56 AM Matt Sicker > wrote: > > >> > > >>> Could be requiring a newer Jenkins version by now ;) > > >>> > > >> > > >> Yes, every 3 months is the plan, when I last upgraded in April, we > were > > >> on the > > >> very latest then, now it's time to upgrade again, and I plan that in > the > > >> next > > >> few days. > > >> > > >> 3 months is about the best we can do and any releases of Jenkins in > > >> between > > >> those times will just have to wait until our next upgrade cycle. > > >> > > >> > > >>> One other plugin I noticed I was using is Warnings NG: > > >>> https://plugins.jenkins.io/warnings-ng/ > > >>> > > >>> On Fri, 17 Jul 2020 at 17:53, Gavin McDonald > > >>> wrote: > > >>> > > > >>> > Hi Matt > > >>> > > > >>> > On Sat, Jul 18, 2020 at 12:35 AM Matt Sicker > > wrote: > > >>> >> > > >>> >> Could you add the Slack plugin? https://plugins.jenkins.io/slack/ > > >>> >> > > >>> > > > >>> > interestingly, that one does not appear on the list of available > > >>> plugins. > > >>> > > > >>> > I'll check into it. > > >>> > > > >>> > > > >>> >> > > >>> >> On Fri, 17 Jul 2020 at 17:27, Gavin McDonald < > gmcdon...@apache.org> > > >>> wrote: > > >>> >> > > > >>> >> > Hi Sebb > > >>> >> > > > >>> >> > On Fri, Jul 17, 2020 at 11:27 PM sebb wrote: > > >>> >> > > > >>> >> > > Also email is not working > > >>> >> > > > > >>> >> > > ERROR: Could not connect to SMTP host: localhost, port: 25 > > >>> >> > > javax.mail.MessagingException: Could not connect to SMTP host: > > >>> localhost, port: 25; > > >>> >> > > nested exception is: > > >>> >> > > java.net.ConnectException: Connection refused > (Connection > > >>> refused) > > >>> >> > > > > >>> >> > > > > >>> >> > Try again please. > > >>> >> > > > >>> >> > > > >>> >> > > > > >>> >> > > > > >>> >> > > On Fri, 17 Jul 2020 at 22:24, Gavin McDonald < > > >>> gmcdon...@apache.org> wrote: > > >>> >> > > > > >>> >> > >> Hi Sebb, > > >>> >> > >> > > >>> >> > >> On Fri, Jul 17, 2020 at 11:04 PM sebb > > wrote: > > >>> >> > >> > > >>> >> > >>> > > >>> >> > >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald < > > >>> gmcdon...@apache.org> > > >>> >> > >>> wrote: > > >>> >> > >>> > > >>> >> > Hi Sebb > > >>> >> > > > >>> >> > On Fri, Jul 17, 2020 at 2:10 PM sebb > > wrote: > > >>> >> > > > >>> >> > > Please create Commons > > >>> >> > > > > >>> >> > > > >>> >> > Added ,please test. > > >>> >> > > > >>> >> > > > >>> >> > >>> Thanks. > > >>> >> > >>> > > >>> >> > >>> Build Pre Steps does not support "Inject Environment > > Variables" > > >>> >> > >>> > > >>> >> > >>> There are far fewer possible types of Pre Step. > > >>> >> > >>> Maybe there are others that are missing; I've only looked at > > >>> one job so > > >>> >> > >>> far. > > >>> >> > >>> > > >>> >> > >> > > >>> >> > >> Thanks, please file an INFRA jira > > >>> >> > >> > > >>> >> > >> > > >>> >> > >>> > > >>> >> > >>> > > >>> >> > -- > > >>> >> > > > >>> >> > *Gavin McDonald* > > >>> >> > Systems Administrator > > >>> >> > ASF Infrastructure Team > > >>> >> > > > >>> >> > >>> > > >>> >> > >> > > >>> >> > >> -- > > >>> >> > >> > > >>> >> > >> *Gavin McDonald* > > >>> >> > >> Systems Administrator > > >>> >> > >> ASF Infrastructure Team > > >>> >> > >> > > >>> >> > > > > >>> >> > > > >>> >> > -- > > >>> >> > > > >>> >> > *Gavin McDonald* > > >>> >> > Systems Administrator > > >>> >> > ASF Infrastructure Team > > >>> >> > > >>> >> > > >>> >> > > >>> >> -- > > >>> >> Matt Sicker > > >>> > > > >>> > > > >>> > > > >>> > -- > > >>> > Gavin McDonald > > >>> > Systems Administrator > > >>> > ASF Infrastructure Team > > >>> > > > >>> > > >>> > > >>> -- > > >>> Matt Sicker > > >>> > > >> > > >> > > >> -- > > >> *Gavin McDonald* > > >> Systems Administrator > > >> ASF Infrastructure Team > > >> > > >> > > > > > > -- > > > Matt Sicker > > > > > > > > > -- > > Matt Sicker > > > > > -- > Olivier Lamy > http://twitter.com/olamy | http://linkedin.com/in/olamy > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Stefan, On Sat, Jul 18, 2020 at 7:42 AM Stefan Seelmann wrote: > Hi Gavin, > > please create a folder for Directory, with edit access for all committers. > > All done, > Kind Regards, > Stefan > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Martin, On Sat, Jul 18, 2020 at 7:14 AM Martin wrote: > Hi Gavin, > > could you please create a folder for Archiva. > Edit access for all commiters. > All done. -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Yes please this one. @Gav can you please create folders for Maven and Archiva? Thanks Olivier On Sat, 18 Jul 2020 at 09:57, Matt Sicker wrote: > One other plugin that might be missing: the gitbox SCM source? Not sure how > to configure webhooks otherwise without creating a personal API token on > GitHub or something. > > On Fri, 17 Jul 2020 at 18:10, Matt Sicker wrote: > > > That's fine with me. The Slack plugin isn't too big a deal since there's > a > > different one available after updating Core in the first place. The > > Warnings NG plugin would be great to get reinstalled, though. > > > > On Fri, 17 Jul 2020 at 18:06, Gavin McDonald > wrote: > > > >> Hi Matt > >> > >> On Sat, Jul 18, 2020 at 12:56 AM Matt Sicker wrote: > >> > >>> Could be requiring a newer Jenkins version by now ;) > >>> > >> > >> Yes, every 3 months is the plan, when I last upgraded in April, we were > >> on the > >> very latest then, now it's time to upgrade again, and I plan that in the > >> next > >> few days. > >> > >> 3 months is about the best we can do and any releases of Jenkins in > >> between > >> those times will just have to wait until our next upgrade cycle. > >> > >> > >>> One other plugin I noticed I was using is Warnings NG: > >>> https://plugins.jenkins.io/warnings-ng/ > >>> > >>> On Fri, 17 Jul 2020 at 17:53, Gavin McDonald > >>> wrote: > >>> > > >>> > Hi Matt > >>> > > >>> > On Sat, Jul 18, 2020 at 12:35 AM Matt Sicker > wrote: > >>> >> > >>> >> Could you add the Slack plugin? https://plugins.jenkins.io/slack/ > >>> >> > >>> > > >>> > interestingly, that one does not appear on the list of available > >>> plugins. > >>> > > >>> > I'll check into it. > >>> > > >>> > > >>> >> > >>> >> On Fri, 17 Jul 2020 at 17:27, Gavin McDonald > >>> wrote: > >>> >> > > >>> >> > Hi Sebb > >>> >> > > >>> >> > On Fri, Jul 17, 2020 at 11:27 PM sebb wrote: > >>> >> > > >>> >> > > Also email is not working > >>> >> > > > >>> >> > > ERROR: Could not connect to SMTP host: localhost, port: 25 > >>> >> > > javax.mail.MessagingException: Could not connect to SMTP host: > >>> localhost, port: 25; > >>> >> > > nested exception is: > >>> >> > > java.net.ConnectException: Connection refused (Connection > >>> refused) > >>> >> > > > >>> >> > > > >>> >> > Try again please. > >>> >> > > >>> >> > > >>> >> > > > >>> >> > > > >>> >> > > On Fri, 17 Jul 2020 at 22:24, Gavin McDonald < > >>> gmcdon...@apache.org> wrote: > >>> >> > > > >>> >> > >> Hi Sebb, > >>> >> > >> > >>> >> > >> On Fri, Jul 17, 2020 at 11:04 PM sebb > wrote: > >>> >> > >> > >>> >> > >>> > >>> >> > >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald < > >>> gmcdon...@apache.org> > >>> >> > >>> wrote: > >>> >> > >>> > >>> >> > Hi Sebb > >>> >> > > >>> >> > On Fri, Jul 17, 2020 at 2:10 PM sebb > wrote: > >>> >> > > >>> >> > > Please create Commons > >>> >> > > > >>> >> > > >>> >> > Added ,please test. > >>> >> > > >>> >> > > >>> >> > >>> Thanks. > >>> >> > >>> > >>> >> > >>> Build Pre Steps does not support "Inject Environment > Variables" > >>> >> > >>> > >>> >> > >>> There are far fewer possible types of Pre Step. > >>> >> > >>> Maybe there are others that are missing; I've only looked at > >>> one job so > >>> >> > >>> far. > >>> >> > >>> > >>> >> > >> > >>> >> > >> Thanks, please file an INFRA jira > >>> >> > >> > >>> >> > >> > >>> >> > >>> > >>> >> > >>> > >>> >> > -- > >>> >> > > >>> >> > *Gavin McDonald* > >>> >> > Systems Administrator > >>> >> > ASF Infrastructure Team > >>> >> > > >>> >> > >>> > >>> >> > >> > >>> >> > >> -- > >>> >> > >> > >>> >> > >> *Gavin McDonald* > >>> >> > >> Systems Administrator > >>> >> > >> ASF Infrastructure Team > >>> >> > >> > >>> >> > > > >>> >> > > >>> >> > -- > >>> >> > > >>> >> > *Gavin McDonald* > >>> >> > Systems Administrator > >>> >> > ASF Infrastructure Team > >>> >> > >>> >> > >>> >> > >>> >> -- > >>> >> Matt Sicker > >>> > > >>> > > >>> > > >>> > -- > >>> > Gavin McDonald > >>> > Systems Administrator > >>> > ASF Infrastructure Team > >>> > > >>> > >>> > >>> -- > >>> Matt Sicker > >>> > >> > >> > >> -- > >> *Gavin McDonald* > >> Systems Administrator > >> ASF Infrastructure Team > >> > >> > > > > -- > > Matt Sicker > > > > > -- > Matt Sicker > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Gavin, please create a folder for Directory, with edit access for all committers. Kind Regards, Stefan
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Gavin, could you please create a folder for Archiva. Edit access for all commiters. Thx Martin Am Donnerstag, 16. Juli 2020, 18:33:08 CEST schrieb Gavin McDonald: > Hi All, > > This NOTICE is for everyone on builds.apache.org. We are migrating to a new > Cloudbees based Client Master called https://ci-builds.apache.org. The > migrations of all jobs needs to be done before the switch off date of 15th > August 2020, so you have a maximum of 4 weeks. > > There is no tool or automated way of migrating your jobs, the > differences in the platforms, the plugins and the setup makes it impossible > to do in a safe way. So, you all need to start creating new jobs on > ci-infra.a.o and then , when you are happy, turn off your old builds on > builds.a.o. > > There are currently 4 agents over there ready to take jobs, plus a floating > agent which is shared amongst many masters (more to come). I will migrate > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > will keep an eye of load across both and adjust accordingly. > > If needed, create a ticket on INFRA jira for any issues that crop up, or > email here on builds@a.o. there may be one or two plugins we need to > install/tweak etc. > > We will be not using 'Views' at the top level, but rather we will take > advantage of 'Folders Plus' - each project will get its own Folder and have > authorisation access to create/edit jobs etc within that folder. I will > create these folders as you ask for them to start with. This setup allows > for credentials isolation amongst other benefits, including but not limited > to exclusive agents (Controlled Agents) for your own use , should you have > any project targeted donations of agents. > > As with other aspects of the ASF, projects can choose to just enable all > committers access to their folder, just ask. > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will not > be setting up any forwarding rules or anything like that. > > So, please, get started *now *on this so you can be sure we are all > completed before the final cutoff date of 15th August 2020. > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > tickets. > > Hadoop and related projects have their own migration path to follow, same > cut off date, Cassandra, Beam, CouchDB have already migrated and are doing > very well in their new homes. > > Lets get going ... > >
Re: [IMPORTANT] - Migration to ci-builds.a.o
PR builds also seems to be not enabled On Sat, 18 Jul 2020 at 08:24, Maxim Solodovnik wrote: > Hello Gavin, > > It seems sonar integration is missing (Credentials dropdown for sonar is > missing) > > On Sat, 18 Jul 2020 at 06:57, Matt Sicker wrote: > >> One other plugin that might be missing: the gitbox SCM source? Not sure >> how >> to configure webhooks otherwise without creating a personal API token on >> GitHub or something. >> >> On Fri, 17 Jul 2020 at 18:10, Matt Sicker wrote: >> >> > That's fine with me. The Slack plugin isn't too big a deal since >> there's a >> > different one available after updating Core in the first place. The >> > Warnings NG plugin would be great to get reinstalled, though. >> > >> > On Fri, 17 Jul 2020 at 18:06, Gavin McDonald >> wrote: >> > >> >> Hi Matt >> >> >> >> On Sat, Jul 18, 2020 at 12:56 AM Matt Sicker wrote: >> >> >> >>> Could be requiring a newer Jenkins version by now ;) >> >>> >> >> >> >> Yes, every 3 months is the plan, when I last upgraded in April, we were >> >> on the >> >> very latest then, now it's time to upgrade again, and I plan that in >> the >> >> next >> >> few days. >> >> >> >> 3 months is about the best we can do and any releases of Jenkins in >> >> between >> >> those times will just have to wait until our next upgrade cycle. >> >> >> >> >> >>> One other plugin I noticed I was using is Warnings NG: >> >>> https://plugins.jenkins.io/warnings-ng/ >> >>> >> >>> On Fri, 17 Jul 2020 at 17:53, Gavin McDonald >> >>> wrote: >> >>> > >> >>> > Hi Matt >> >>> > >> >>> > On Sat, Jul 18, 2020 at 12:35 AM Matt Sicker >> wrote: >> >>> >> >> >>> >> Could you add the Slack plugin? https://plugins.jenkins.io/slack/ >> >>> >> >> >>> > >> >>> > interestingly, that one does not appear on the list of available >> >>> plugins. >> >>> > >> >>> > I'll check into it. >> >>> > >> >>> > >> >>> >> >> >>> >> On Fri, 17 Jul 2020 at 17:27, Gavin McDonald > > >> >>> wrote: >> >>> >> > >> >>> >> > Hi Sebb >> >>> >> > >> >>> >> > On Fri, Jul 17, 2020 at 11:27 PM sebb wrote: >> >>> >> > >> >>> >> > > Also email is not working >> >>> >> > > >> >>> >> > > ERROR: Could not connect to SMTP host: localhost, port: 25 >> >>> >> > > javax.mail.MessagingException: Could not connect to SMTP host: >> >>> localhost, port: 25; >> >>> >> > > nested exception is: >> >>> >> > > java.net.ConnectException: Connection refused (Connection >> >>> refused) >> >>> >> > > >> >>> >> > > >> >>> >> > Try again please. >> >>> >> > >> >>> >> > >> >>> >> > > >> >>> >> > > >> >>> >> > > On Fri, 17 Jul 2020 at 22:24, Gavin McDonald < >> >>> gmcdon...@apache.org> wrote: >> >>> >> > > >> >>> >> > >> Hi Sebb, >> >>> >> > >> >> >>> >> > >> On Fri, Jul 17, 2020 at 11:04 PM sebb >> wrote: >> >>> >> > >> >> >>> >> > >>> >> >>> >> > >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald < >> >>> gmcdon...@apache.org> >> >>> >> > >>> wrote: >> >>> >> > >>> >> >>> >> > Hi Sebb >> >>> >> > >> >>> >> > On Fri, Jul 17, 2020 at 2:10 PM sebb >> wrote: >> >>> >> > >> >>> >> > > Please create Commons >> >>> >> > > >> >>> >> > >> >>> >> > Added ,please test. >> >>> >> > >> >>> >> > >> >>> >> > >>> Thanks. >> >>> >> > >>> >> >>> >> > >>> Build Pre Steps does not support "Inject Environment >> Variables" >> >>> >> > >>> >> >>> >> > >>> There are far fewer possible types of Pre Step. >> >>> >> > >>> Maybe there are others that are missing; I've only looked at >> >>> one job so >> >>> >> > >>> far. >> >>> >> > >>> >> >>> >> > >> >> >>> >> > >> Thanks, please file an INFRA jira >> >>> >> > >> >> >>> >> > >> >> >>> >> > >>> >> >>> >> > >>> >> >>> >> > -- >> >>> >> > >> >>> >> > *Gavin McDonald* >> >>> >> > Systems Administrator >> >>> >> > ASF Infrastructure Team >> >>> >> > >> >>> >> > >>> >> >>> >> > >> >> >>> >> > >> -- >> >>> >> > >> >> >>> >> > >> *Gavin McDonald* >> >>> >> > >> Systems Administrator >> >>> >> > >> ASF Infrastructure Team >> >>> >> > >> >> >>> >> > > >> >>> >> > >> >>> >> > -- >> >>> >> > >> >>> >> > *Gavin McDonald* >> >>> >> > Systems Administrator >> >>> >> > ASF Infrastructure Team >> >>> >> >> >>> >> >> >>> >> >> >>> >> -- >> >>> >> Matt Sicker >> >>> > >> >>> > >> >>> > >> >>> > -- >> >>> > Gavin McDonald >> >>> > Systems Administrator >> >>> > ASF Infrastructure Team >> >>> > >> >>> >> >>> >> >>> -- >> >>> Matt Sicker >> >>> >> >> >> >> >> >> -- >> >> *Gavin McDonald* >> >> Systems Administrator >> >> ASF Infrastructure Team >> >> >> >> >> > >> > -- >> > Matt Sicker >> > >> >> >> -- >> Matt Sicker >> > > > -- > Best regards, > Maxim > -- Best regards, Maxim
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hello Gavin, It seems sonar integration is missing (Credentials dropdown for sonar is missing) On Sat, 18 Jul 2020 at 06:57, Matt Sicker wrote: > One other plugin that might be missing: the gitbox SCM source? Not sure how > to configure webhooks otherwise without creating a personal API token on > GitHub or something. > > On Fri, 17 Jul 2020 at 18:10, Matt Sicker wrote: > > > That's fine with me. The Slack plugin isn't too big a deal since there's > a > > different one available after updating Core in the first place. The > > Warnings NG plugin would be great to get reinstalled, though. > > > > On Fri, 17 Jul 2020 at 18:06, Gavin McDonald > wrote: > > > >> Hi Matt > >> > >> On Sat, Jul 18, 2020 at 12:56 AM Matt Sicker wrote: > >> > >>> Could be requiring a newer Jenkins version by now ;) > >>> > >> > >> Yes, every 3 months is the plan, when I last upgraded in April, we were > >> on the > >> very latest then, now it's time to upgrade again, and I plan that in the > >> next > >> few days. > >> > >> 3 months is about the best we can do and any releases of Jenkins in > >> between > >> those times will just have to wait until our next upgrade cycle. > >> > >> > >>> One other plugin I noticed I was using is Warnings NG: > >>> https://plugins.jenkins.io/warnings-ng/ > >>> > >>> On Fri, 17 Jul 2020 at 17:53, Gavin McDonald > >>> wrote: > >>> > > >>> > Hi Matt > >>> > > >>> > On Sat, Jul 18, 2020 at 12:35 AM Matt Sicker > wrote: > >>> >> > >>> >> Could you add the Slack plugin? https://plugins.jenkins.io/slack/ > >>> >> > >>> > > >>> > interestingly, that one does not appear on the list of available > >>> plugins. > >>> > > >>> > I'll check into it. > >>> > > >>> > > >>> >> > >>> >> On Fri, 17 Jul 2020 at 17:27, Gavin McDonald > >>> wrote: > >>> >> > > >>> >> > Hi Sebb > >>> >> > > >>> >> > On Fri, Jul 17, 2020 at 11:27 PM sebb wrote: > >>> >> > > >>> >> > > Also email is not working > >>> >> > > > >>> >> > > ERROR: Could not connect to SMTP host: localhost, port: 25 > >>> >> > > javax.mail.MessagingException: Could not connect to SMTP host: > >>> localhost, port: 25; > >>> >> > > nested exception is: > >>> >> > > java.net.ConnectException: Connection refused (Connection > >>> refused) > >>> >> > > > >>> >> > > > >>> >> > Try again please. > >>> >> > > >>> >> > > >>> >> > > > >>> >> > > > >>> >> > > On Fri, 17 Jul 2020 at 22:24, Gavin McDonald < > >>> gmcdon...@apache.org> wrote: > >>> >> > > > >>> >> > >> Hi Sebb, > >>> >> > >> > >>> >> > >> On Fri, Jul 17, 2020 at 11:04 PM sebb > wrote: > >>> >> > >> > >>> >> > >>> > >>> >> > >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald < > >>> gmcdon...@apache.org> > >>> >> > >>> wrote: > >>> >> > >>> > >>> >> > Hi Sebb > >>> >> > > >>> >> > On Fri, Jul 17, 2020 at 2:10 PM sebb > wrote: > >>> >> > > >>> >> > > Please create Commons > >>> >> > > > >>> >> > > >>> >> > Added ,please test. > >>> >> > > >>> >> > > >>> >> > >>> Thanks. > >>> >> > >>> > >>> >> > >>> Build Pre Steps does not support "Inject Environment > Variables" > >>> >> > >>> > >>> >> > >>> There are far fewer possible types of Pre Step. > >>> >> > >>> Maybe there are others that are missing; I've only looked at > >>> one job so > >>> >> > >>> far. > >>> >> > >>> > >>> >> > >> > >>> >> > >> Thanks, please file an INFRA jira > >>> >> > >> > >>> >> > >> > >>> >> > >>> > >>> >> > >>> > >>> >> > -- > >>> >> > > >>> >> > *Gavin McDonald* > >>> >> > Systems Administrator > >>> >> > ASF Infrastructure Team > >>> >> > > >>> >> > >>> > >>> >> > >> > >>> >> > >> -- > >>> >> > >> > >>> >> > >> *Gavin McDonald* > >>> >> > >> Systems Administrator > >>> >> > >> ASF Infrastructure Team > >>> >> > >> > >>> >> > > > >>> >> > > >>> >> > -- > >>> >> > > >>> >> > *Gavin McDonald* > >>> >> > Systems Administrator > >>> >> > ASF Infrastructure Team > >>> >> > >>> >> > >>> >> > >>> >> -- > >>> >> Matt Sicker > >>> > > >>> > > >>> > > >>> > -- > >>> > Gavin McDonald > >>> > Systems Administrator > >>> > ASF Infrastructure Team > >>> > > >>> > >>> > >>> -- > >>> Matt Sicker > >>> > >> > >> > >> -- > >> *Gavin McDonald* > >> Systems Administrator > >> ASF Infrastructure Team > >> > >> > > > > -- > > Matt Sicker > > > > > -- > Matt Sicker > -- Best regards, Maxim
Re: [IMPORTANT] - Migration to ci-builds.a.o
One other plugin that might be missing: the gitbox SCM source? Not sure how to configure webhooks otherwise without creating a personal API token on GitHub or something. On Fri, 17 Jul 2020 at 18:10, Matt Sicker wrote: > That's fine with me. The Slack plugin isn't too big a deal since there's a > different one available after updating Core in the first place. The > Warnings NG plugin would be great to get reinstalled, though. > > On Fri, 17 Jul 2020 at 18:06, Gavin McDonald wrote: > >> Hi Matt >> >> On Sat, Jul 18, 2020 at 12:56 AM Matt Sicker wrote: >> >>> Could be requiring a newer Jenkins version by now ;) >>> >> >> Yes, every 3 months is the plan, when I last upgraded in April, we were >> on the >> very latest then, now it's time to upgrade again, and I plan that in the >> next >> few days. >> >> 3 months is about the best we can do and any releases of Jenkins in >> between >> those times will just have to wait until our next upgrade cycle. >> >> >>> One other plugin I noticed I was using is Warnings NG: >>> https://plugins.jenkins.io/warnings-ng/ >>> >>> On Fri, 17 Jul 2020 at 17:53, Gavin McDonald >>> wrote: >>> > >>> > Hi Matt >>> > >>> > On Sat, Jul 18, 2020 at 12:35 AM Matt Sicker wrote: >>> >> >>> >> Could you add the Slack plugin? https://plugins.jenkins.io/slack/ >>> >> >>> > >>> > interestingly, that one does not appear on the list of available >>> plugins. >>> > >>> > I'll check into it. >>> > >>> > >>> >> >>> >> On Fri, 17 Jul 2020 at 17:27, Gavin McDonald >>> wrote: >>> >> > >>> >> > Hi Sebb >>> >> > >>> >> > On Fri, Jul 17, 2020 at 11:27 PM sebb wrote: >>> >> > >>> >> > > Also email is not working >>> >> > > >>> >> > > ERROR: Could not connect to SMTP host: localhost, port: 25 >>> >> > > javax.mail.MessagingException: Could not connect to SMTP host: >>> localhost, port: 25; >>> >> > > nested exception is: >>> >> > > java.net.ConnectException: Connection refused (Connection >>> refused) >>> >> > > >>> >> > > >>> >> > Try again please. >>> >> > >>> >> > >>> >> > > >>> >> > > >>> >> > > On Fri, 17 Jul 2020 at 22:24, Gavin McDonald < >>> gmcdon...@apache.org> wrote: >>> >> > > >>> >> > >> Hi Sebb, >>> >> > >> >>> >> > >> On Fri, Jul 17, 2020 at 11:04 PM sebb wrote: >>> >> > >> >>> >> > >>> >>> >> > >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald < >>> gmcdon...@apache.org> >>> >> > >>> wrote: >>> >> > >>> >>> >> > Hi Sebb >>> >> > >>> >> > On Fri, Jul 17, 2020 at 2:10 PM sebb wrote: >>> >> > >>> >> > > Please create Commons >>> >> > > >>> >> > >>> >> > Added ,please test. >>> >> > >>> >> > >>> >> > >>> Thanks. >>> >> > >>> >>> >> > >>> Build Pre Steps does not support "Inject Environment Variables" >>> >> > >>> >>> >> > >>> There are far fewer possible types of Pre Step. >>> >> > >>> Maybe there are others that are missing; I've only looked at >>> one job so >>> >> > >>> far. >>> >> > >>> >>> >> > >> >>> >> > >> Thanks, please file an INFRA jira >>> >> > >> >>> >> > >> >>> >> > >>> >>> >> > >>> >>> >> > -- >>> >> > >>> >> > *Gavin McDonald* >>> >> > Systems Administrator >>> >> > ASF Infrastructure Team >>> >> > >>> >> > >>> >>> >> > >> >>> >> > >> -- >>> >> > >> >>> >> > >> *Gavin McDonald* >>> >> > >> Systems Administrator >>> >> > >> ASF Infrastructure Team >>> >> > >> >>> >> > > >>> >> > >>> >> > -- >>> >> > >>> >> > *Gavin McDonald* >>> >> > Systems Administrator >>> >> > ASF Infrastructure Team >>> >> >>> >> >>> >> >>> >> -- >>> >> Matt Sicker >>> > >>> > >>> > >>> > -- >>> > Gavin McDonald >>> > Systems Administrator >>> > ASF Infrastructure Team >>> > >>> >>> >>> -- >>> Matt Sicker >>> >> >> >> -- >> *Gavin McDonald* >> Systems Administrator >> ASF Infrastructure Team >> >> > > -- > Matt Sicker > -- Matt Sicker
Re: [IMPORTANT] - Migration to ci-builds.a.o
That's fine with me. The Slack plugin isn't too big a deal since there's a different one available after updating Core in the first place. The Warnings NG plugin would be great to get reinstalled, though. On Fri, 17 Jul 2020 at 18:06, Gavin McDonald wrote: > Hi Matt > > On Sat, Jul 18, 2020 at 12:56 AM Matt Sicker wrote: > >> Could be requiring a newer Jenkins version by now ;) >> > > Yes, every 3 months is the plan, when I last upgraded in April, we were on > the > very latest then, now it's time to upgrade again, and I plan that in the > next > few days. > > 3 months is about the best we can do and any releases of Jenkins in > between > those times will just have to wait until our next upgrade cycle. > > >> One other plugin I noticed I was using is Warnings NG: >> https://plugins.jenkins.io/warnings-ng/ >> >> On Fri, 17 Jul 2020 at 17:53, Gavin McDonald >> wrote: >> > >> > Hi Matt >> > >> > On Sat, Jul 18, 2020 at 12:35 AM Matt Sicker wrote: >> >> >> >> Could you add the Slack plugin? https://plugins.jenkins.io/slack/ >> >> >> > >> > interestingly, that one does not appear on the list of available >> plugins. >> > >> > I'll check into it. >> > >> > >> >> >> >> On Fri, 17 Jul 2020 at 17:27, Gavin McDonald >> wrote: >> >> > >> >> > Hi Sebb >> >> > >> >> > On Fri, Jul 17, 2020 at 11:27 PM sebb wrote: >> >> > >> >> > > Also email is not working >> >> > > >> >> > > ERROR: Could not connect to SMTP host: localhost, port: 25 >> >> > > javax.mail.MessagingException: Could not connect to SMTP host: >> localhost, port: 25; >> >> > > nested exception is: >> >> > > java.net.ConnectException: Connection refused (Connection >> refused) >> >> > > >> >> > > >> >> > Try again please. >> >> > >> >> > >> >> > > >> >> > > >> >> > > On Fri, 17 Jul 2020 at 22:24, Gavin McDonald >> wrote: >> >> > > >> >> > >> Hi Sebb, >> >> > >> >> >> > >> On Fri, Jul 17, 2020 at 11:04 PM sebb wrote: >> >> > >> >> >> > >>> >> >> > >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald < >> gmcdon...@apache.org> >> >> > >>> wrote: >> >> > >>> >> >> > Hi Sebb >> >> > >> >> > On Fri, Jul 17, 2020 at 2:10 PM sebb wrote: >> >> > >> >> > > Please create Commons >> >> > > >> >> > >> >> > Added ,please test. >> >> > >> >> > >> >> > >>> Thanks. >> >> > >>> >> >> > >>> Build Pre Steps does not support "Inject Environment Variables" >> >> > >>> >> >> > >>> There are far fewer possible types of Pre Step. >> >> > >>> Maybe there are others that are missing; I've only looked at one >> job so >> >> > >>> far. >> >> > >>> >> >> > >> >> >> > >> Thanks, please file an INFRA jira >> >> > >> >> >> > >> >> >> > >>> >> >> > >>> >> >> > -- >> >> > >> >> > *Gavin McDonald* >> >> > Systems Administrator >> >> > ASF Infrastructure Team >> >> > >> >> > >>> >> >> > >> >> >> > >> -- >> >> > >> >> >> > >> *Gavin McDonald* >> >> > >> Systems Administrator >> >> > >> ASF Infrastructure Team >> >> > >> >> >> > > >> >> > >> >> > -- >> >> > >> >> > *Gavin McDonald* >> >> > Systems Administrator >> >> > ASF Infrastructure Team >> >> >> >> >> >> >> >> -- >> >> Matt Sicker >> > >> > >> > >> > -- >> > Gavin McDonald >> > Systems Administrator >> > ASF Infrastructure Team >> > >> >> >> -- >> Matt Sicker >> > > > -- > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team > > -- Matt Sicker
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Matt On Sat, Jul 18, 2020 at 12:56 AM Matt Sicker wrote: > Could be requiring a newer Jenkins version by now ;) > Yes, every 3 months is the plan, when I last upgraded in April, we were on the very latest then, now it's time to upgrade again, and I plan that in the next few days. 3 months is about the best we can do and any releases of Jenkins in between those times will just have to wait until our next upgrade cycle. > One other plugin I noticed I was using is Warnings NG: > https://plugins.jenkins.io/warnings-ng/ > > On Fri, 17 Jul 2020 at 17:53, Gavin McDonald wrote: > > > > Hi Matt > > > > On Sat, Jul 18, 2020 at 12:35 AM Matt Sicker wrote: > >> > >> Could you add the Slack plugin? https://plugins.jenkins.io/slack/ > >> > > > > interestingly, that one does not appear on the list of available plugins. > > > > I'll check into it. > > > > > >> > >> On Fri, 17 Jul 2020 at 17:27, Gavin McDonald > wrote: > >> > > >> > Hi Sebb > >> > > >> > On Fri, Jul 17, 2020 at 11:27 PM sebb wrote: > >> > > >> > > Also email is not working > >> > > > >> > > ERROR: Could not connect to SMTP host: localhost, port: 25 > >> > > javax.mail.MessagingException: Could not connect to SMTP host: > localhost, port: 25; > >> > > nested exception is: > >> > > java.net.ConnectException: Connection refused (Connection > refused) > >> > > > >> > > > >> > Try again please. > >> > > >> > > >> > > > >> > > > >> > > On Fri, 17 Jul 2020 at 22:24, Gavin McDonald > wrote: > >> > > > >> > >> Hi Sebb, > >> > >> > >> > >> On Fri, Jul 17, 2020 at 11:04 PM sebb wrote: > >> > >> > >> > >>> > >> > >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald < > gmcdon...@apache.org> > >> > >>> wrote: > >> > >>> > >> > Hi Sebb > >> > > >> > On Fri, Jul 17, 2020 at 2:10 PM sebb wrote: > >> > > >> > > Please create Commons > >> > > > >> > > >> > Added ,please test. > >> > > >> > > >> > >>> Thanks. > >> > >>> > >> > >>> Build Pre Steps does not support "Inject Environment Variables" > >> > >>> > >> > >>> There are far fewer possible types of Pre Step. > >> > >>> Maybe there are others that are missing; I've only looked at one > job so > >> > >>> far. > >> > >>> > >> > >> > >> > >> Thanks, please file an INFRA jira > >> > >> > >> > >> > >> > >>> > >> > >>> > >> > -- > >> > > >> > *Gavin McDonald* > >> > Systems Administrator > >> > ASF Infrastructure Team > >> > > >> > >>> > >> > >> > >> > >> -- > >> > >> > >> > >> *Gavin McDonald* > >> > >> Systems Administrator > >> > >> ASF Infrastructure Team > >> > >> > >> > > > >> > > >> > -- > >> > > >> > *Gavin McDonald* > >> > Systems Administrator > >> > ASF Infrastructure Team > >> > >> > >> > >> -- > >> Matt Sicker > > > > > > > > -- > > Gavin McDonald > > Systems Administrator > > ASF Infrastructure Team > > > > > -- > Matt Sicker > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Could be requiring a newer Jenkins version by now ;) One other plugin I noticed I was using is Warnings NG: https://plugins.jenkins.io/warnings-ng/ On Fri, 17 Jul 2020 at 17:53, Gavin McDonald wrote: > > Hi Matt > > On Sat, Jul 18, 2020 at 12:35 AM Matt Sicker wrote: >> >> Could you add the Slack plugin? https://plugins.jenkins.io/slack/ >> > > interestingly, that one does not appear on the list of available plugins. > > I'll check into it. > > >> >> On Fri, 17 Jul 2020 at 17:27, Gavin McDonald wrote: >> > >> > Hi Sebb >> > >> > On Fri, Jul 17, 2020 at 11:27 PM sebb wrote: >> > >> > > Also email is not working >> > > >> > > ERROR: Could not connect to SMTP host: localhost, port: 25 >> > > javax.mail.MessagingException: Could not connect to SMTP host: >> > > localhost, port: 25; >> > > nested exception is: >> > > java.net.ConnectException: Connection refused (Connection refused) >> > > >> > > >> > Try again please. >> > >> > >> > > >> > > >> > > On Fri, 17 Jul 2020 at 22:24, Gavin McDonald >> > > wrote: >> > > >> > >> Hi Sebb, >> > >> >> > >> On Fri, Jul 17, 2020 at 11:04 PM sebb wrote: >> > >> >> > >>> >> > >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald >> > >>> wrote: >> > >>> >> > Hi Sebb >> > >> > On Fri, Jul 17, 2020 at 2:10 PM sebb wrote: >> > >> > > Please create Commons >> > > >> > >> > Added ,please test. >> > >> > >> > >>> Thanks. >> > >>> >> > >>> Build Pre Steps does not support "Inject Environment Variables" >> > >>> >> > >>> There are far fewer possible types of Pre Step. >> > >>> Maybe there are others that are missing; I've only looked at one job so >> > >>> far. >> > >>> >> > >> >> > >> Thanks, please file an INFRA jira >> > >> >> > >> >> > >>> >> > >>> >> > -- >> > >> > *Gavin McDonald* >> > Systems Administrator >> > ASF Infrastructure Team >> > >> > >>> >> > >> >> > >> -- >> > >> >> > >> *Gavin McDonald* >> > >> Systems Administrator >> > >> ASF Infrastructure Team >> > >> >> > > >> > >> > -- >> > >> > *Gavin McDonald* >> > Systems Administrator >> > ASF Infrastructure Team >> >> >> >> -- >> Matt Sicker > > > > -- > Gavin McDonald > Systems Administrator > ASF Infrastructure Team > -- Matt Sicker
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Matt On Sat, Jul 18, 2020 at 12:35 AM Matt Sicker wrote: > Could you add the Slack plugin? https://plugins.jenkins.io/slack/ > > interestingly, that one does not appear on the list of available plugins. I'll check into it. > On Fri, 17 Jul 2020 at 17:27, Gavin McDonald wrote: > > > > Hi Sebb > > > > On Fri, Jul 17, 2020 at 11:27 PM sebb wrote: > > > > > Also email is not working > > > > > > ERROR: Could not connect to SMTP host: localhost, port: 25 > > > javax.mail.MessagingException: Could not connect to SMTP host: > localhost, port: 25; > > > nested exception is: > > > java.net.ConnectException: Connection refused (Connection > refused) > > > > > > > > Try again please. > > > > > > > > > > > > > On Fri, 17 Jul 2020 at 22:24, Gavin McDonald > wrote: > > > > > >> Hi Sebb, > > >> > > >> On Fri, Jul 17, 2020 at 11:04 PM sebb wrote: > > >> > > >>> > > >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald > > >>> wrote: > > >>> > > Hi Sebb > > > > On Fri, Jul 17, 2020 at 2:10 PM sebb wrote: > > > > > Please create Commons > > > > > > > Added ,please test. > > > > > > >>> Thanks. > > >>> > > >>> Build Pre Steps does not support "Inject Environment Variables" > > >>> > > >>> There are far fewer possible types of Pre Step. > > >>> Maybe there are others that are missing; I've only looked at one job > so > > >>> far. > > >>> > > >> > > >> Thanks, please file an INFRA jira > > >> > > >> > > >>> > > >>> > > -- > > > > *Gavin McDonald* > > Systems Administrator > > ASF Infrastructure Team > > > > >>> > > >> > > >> -- > > >> > > >> *Gavin McDonald* > > >> Systems Administrator > > >> ASF Infrastructure Team > > >> > > > > > > > -- > > > > *Gavin McDonald* > > Systems Administrator > > ASF Infrastructure Team > > > > -- > Matt Sicker > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Gavin, Could you please create a folder for Guacamole, with access granted to all Guacamole committers? Thanks, - Mike On Thu, Jul 16, 2020, 09:33 Gavin McDonald wrote: > Hi All, > > This NOTICE is for everyone on builds.apache.org. We are migrating to a > new > Cloudbees based Client Master called https://ci-builds.apache.org. The > migrations of all jobs needs to be done before the switch off date of 15th > August 2020, so you have a maximum of 4 weeks. > > There is no tool or automated way of migrating your jobs, the > differences in the platforms, the plugins and the setup makes it impossible > to do in a safe way. So, you all need to start creating new jobs on > ci-infra.a.o and then , when you are happy, turn off your old builds on > builds.a.o. > > There are currently 4 agents over there ready to take jobs, plus a floating > agent which is shared amongst many masters (more to come). I will migrate > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > will keep an eye of load across both and adjust accordingly. > > If needed, create a ticket on INFRA jira for any issues that crop up, or > email here on builds@a.o. there may be one or two plugins we need to > install/tweak etc. > > We will be not using 'Views' at the top level, but rather we will take > advantage of 'Folders Plus' - each project will get its own Folder and have > authorisation access to create/edit jobs etc within that folder. I will > create these folders as you ask for them to start with. This setup allows > for credentials isolation amongst other benefits, including but not limited > to exclusive agents (Controlled Agents) for your own use , should you have > any project targeted donations of agents. > > As with other aspects of the ASF, projects can choose to just enable all > committers access to their folder, just ask. > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will not > be setting up any forwarding rules or anything like that. > > So, please, get started *now *on this so you can be sure we are all > completed before the final cutoff date of 15th August 2020. > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > tickets. > > Hadoop and related projects have their own migration path to follow, same > cut off date, Cassandra, Beam, CouchDB have already migrated and are doing > very well in their new homes. > > Lets get going ... > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team >
Re: [IMPORTANT] - Migration to ci-builds.a.o
Could you add the Slack plugin? https://plugins.jenkins.io/slack/ On Fri, 17 Jul 2020 at 17:27, Gavin McDonald wrote: > > Hi Sebb > > On Fri, Jul 17, 2020 at 11:27 PM sebb wrote: > > > Also email is not working > > > > ERROR: Could not connect to SMTP host: localhost, port: 25 > > javax.mail.MessagingException: Could not connect to SMTP host: localhost, > > port: 25; > > nested exception is: > > java.net.ConnectException: Connection refused (Connection refused) > > > > > Try again please. > > > > > > > > On Fri, 17 Jul 2020 at 22:24, Gavin McDonald wrote: > > > >> Hi Sebb, > >> > >> On Fri, Jul 17, 2020 at 11:04 PM sebb wrote: > >> > >>> > >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald > >>> wrote: > >>> > Hi Sebb > > On Fri, Jul 17, 2020 at 2:10 PM sebb wrote: > > > Please create Commons > > > > Added ,please test. > > > >>> Thanks. > >>> > >>> Build Pre Steps does not support "Inject Environment Variables" > >>> > >>> There are far fewer possible types of Pre Step. > >>> Maybe there are others that are missing; I've only looked at one job so > >>> far. > >>> > >> > >> Thanks, please file an INFRA jira > >> > >> > >>> > >>> > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team > > >>> > >> > >> -- > >> > >> *Gavin McDonald* > >> Systems Administrator > >> ASF Infrastructure Team > >> > > > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team -- Matt Sicker
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Sebb On Fri, Jul 17, 2020 at 11:27 PM sebb wrote: > Also email is not working > > ERROR: Could not connect to SMTP host: localhost, port: 25 > javax.mail.MessagingException: Could not connect to SMTP host: localhost, > port: 25; > nested exception is: > java.net.ConnectException: Connection refused (Connection refused) > > Try again please. > > > On Fri, 17 Jul 2020 at 22:24, Gavin McDonald wrote: > >> Hi Sebb, >> >> On Fri, Jul 17, 2020 at 11:04 PM sebb wrote: >> >>> >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald >>> wrote: >>> Hi Sebb On Fri, Jul 17, 2020 at 2:10 PM sebb wrote: > Please create Commons > Added ,please test. >>> Thanks. >>> >>> Build Pre Steps does not support "Inject Environment Variables" >>> >>> There are far fewer possible types of Pre Step. >>> Maybe there are others that are missing; I've only looked at one job so >>> far. >>> >> >> Thanks, please file an INFRA jira >> >> >>> >>> -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team >>> >> >> -- >> >> *Gavin McDonald* >> Systems Administrator >> ASF Infrastructure Team >> > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Also email is not working ERROR: Could not connect to SMTP host: localhost, port: 25 javax.mail.MessagingException: Could not connect to SMTP host: localhost, port: 25; nested exception is: java.net.ConnectException: Connection refused (Connection refused) On Fri, 17 Jul 2020 at 22:24, Gavin McDonald wrote: > Hi Sebb, > > On Fri, Jul 17, 2020 at 11:04 PM sebb wrote: > >> >> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald >> wrote: >> >>> Hi Sebb >>> >>> On Fri, Jul 17, 2020 at 2:10 PM sebb wrote: >>> Please create Commons >>> >>> Added ,please test. >>> >>> >> Thanks. >> >> Build Pre Steps does not support "Inject Environment Variables" >> >> There are far fewer possible types of Pre Step. >> Maybe there are others that are missing; I've only looked at one job so >> far. >> > > Thanks, please file an INFRA jira > > >> >> >>> -- >>> >>> *Gavin McDonald* >>> Systems Administrator >>> ASF Infrastructure Team >>> >> > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team >
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Sebb, On Fri, Jul 17, 2020 at 11:04 PM sebb wrote: > > On Fri, 17 Jul 2020 at 19:49, Gavin McDonald wrote: > >> Hi Sebb >> >> On Fri, Jul 17, 2020 at 2:10 PM sebb wrote: >> >>> Please create Commons >>> >> >> Added ,please test. >> >> > Thanks. > > Build Pre Steps does not support "Inject Environment Variables" > > There are far fewer possible types of Pre Step. > Maybe there are others that are missing; I've only looked at one job so > far. > Thanks, please file an INFRA jira > > >> -- >> >> *Gavin McDonald* >> Systems Administrator >> ASF Infrastructure Team >> > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
On Fri, 17 Jul 2020 at 19:49, Gavin McDonald wrote: > Hi Sebb > > On Fri, Jul 17, 2020 at 2:10 PM sebb wrote: > >> Please create Commons >> > > Added ,please test. > > Thanks. Build Pre Steps does not support "Inject Environment Variables" There are far fewer possible types of Pre Step. Maybe there are others that are missing; I've only looked at one job so far. > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team >
Re: [IMPORTANT] - Migration to ci-builds.a.o
Please create a folder for Jena, with rights for all Jena committers. Thanks Andy On 16/07/2020 17:33, Gavin McDonald wrote: Hi All, This NOTICE is for everyone on builds.apache.org. We are migrating to a new Cloudbees based Client Master called https://ci-builds.apache.org. The migrations of all jobs needs to be done before the switch off date of 15th August 2020, so you have a maximum of 4 weeks. There is no tool or automated way of migrating your jobs, the differences in the platforms, the plugins and the setup makes it impossible to do in a safe way. So, you all need to start creating new jobs on ci-infra.a.o and then , when you are happy, turn off your old builds on builds.a.o. There are currently 4 agents over there ready to take jobs, plus a floating agent which is shared amongst many masters (more to come). I will migrate away 2 more agents from builds.a.o to ci-builds.a.o every few days, and will keep an eye of load across both and adjust accordingly. If needed, create a ticket on INFRA jira for any issues that crop up, or email here on builds@a.o. there may be one or two plugins we need to install/tweak etc. We will be not using 'Views' at the top level, but rather we will take advantage of 'Folders Plus' - each project will get its own Folder and have authorisation access to create/edit jobs etc within that folder. I will create these folders as you ask for them to start with. This setup allows for credentials isolation amongst other benefits, including but not limited to exclusive agents (Controlled Agents) for your own use , should you have any project targeted donations of agents. As with other aspects of the ASF, projects can choose to just enable all committers access to their folder, just ask. We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will not be setting up any forwarding rules or anything like that. So, please, get started *now *on this so you can be sure we are all completed before the final cutoff date of 15th August 2020. Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA tickets. Hadoop and related projects have their own migration path to follow, same cut off date, Cassandra, Beam, CouchDB have already migrated and are doing very well in their new homes. Lets get going ...
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Gavin, Can you please add a folder for Rya - access for all committers? Thanks, Adina On Thu, Jul 16, 2020 at 12:33 PM Gavin McDonald wrote: > Hi All, > > This NOTICE is for everyone on builds.apache.org. We are migrating to a > new > Cloudbees based Client Master called https://ci-builds.apache.org. The > migrations of all jobs needs to be done before the switch off date of 15th > August 2020, so you have a maximum of 4 weeks. > > There is no tool or automated way of migrating your jobs, the > differences in the platforms, the plugins and the setup makes it impossible > to do in a safe way. So, you all need to start creating new jobs on > ci-infra.a.o and then , when you are happy, turn off your old builds on > builds.a.o. > > There are currently 4 agents over there ready to take jobs, plus a floating > agent which is shared amongst many masters (more to come). I will migrate > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > will keep an eye of load across both and adjust accordingly. > > If needed, create a ticket on INFRA jira for any issues that crop up, or > email here on builds@a.o. there may be one or two plugins we need to > install/tweak etc. > > We will be not using 'Views' at the top level, but rather we will take > advantage of 'Folders Plus' - each project will get its own Folder and have > authorisation access to create/edit jobs etc within that folder. I will > create these folders as you ask for them to start with. This setup allows > for credentials isolation amongst other benefits, including but not limited > to exclusive agents (Controlled Agents) for your own use , should you have > any project targeted donations of agents. > > As with other aspects of the ASF, projects can choose to just enable all > committers access to their folder, just ask. > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will not > be setting up any forwarding rules or anything like that. > > So, please, get started *now *on this so you can be sure we are all > completed before the final cutoff date of 15th August 2020. > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > tickets. > > Hadoop and related projects have their own migration path to follow, same > cut off date, Cassandra, Beam, CouchDB have already migrated and are doing > very well in their new homes. > > Lets get going ... > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team > -- Dr. Adina Crainiceanu Associate Professor Computer Science Department United States Naval Academy 410-293-6822 ad...@usna.edu http://www.usna.edu/Users/cs/adina/
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Phil, On Fri, Jul 17, 2020 at 8:21 PM P. Ottlinger wrote: > Hi Gav, > > can you create a Creadur as well with the right to create jobs for all > PMC-members? > Done, but I extended the scope slightly to all Creadur Committers - I dont see why this should just be PMC Members creating Jenkins jobs, please do let me know if I did the wrong thing there. > > I filed https://issues.apache.org/jira/browse/INFRA-20535 as well. > > Thanks / cheers, > Phil > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Eric On Fri, Jul 17, 2020 at 3:02 PM Eric Barboni wrote: > Hi, > Would it be possible to create NetBeans folder. Access to commiters. > All done, thank you. > > Regards > Eric > > -Message d'origine- > De : sebb > Envoyé : vendredi 17 juillet 2020 14:11 > À : builds > Cc : Gav > Objet : Re: [IMPORTANT] - Migration to ci-builds.a.o > > Please create Commons > > On Fri, 17 Jul 2020 at 12:41, Oleg Kalnichevski > wrote: > > > > On Thu, 2020-07-16 at 22:25 +0100, sebb wrote: > > > On Thu, 16 Jul 2020 at 17:33, Gavin McDonald > > > wrote: > > > > > > > > Hi All, > > > > > > > > This NOTICE is for everyone on builds.apache.org. We are migrating > > > > to a new Cloudbees based Client Master called > > > > https://ci-builds.apache.org. > > > > The > > > > migrations of all jobs needs to be done before the switch off date > > > > of 15th August 2020, so you have a maximum of 4 weeks. > > > > > > > > There is no tool or automated way of migrating your jobs, the > > > > differences in the platforms, the plugins and the setup makes it > > > > impossible to do in a safe way. So, you all need to start creating > > > > new jobs on ci-infra.a.o and then , when you are happy, turn off > > > > your old builds on builds.a.o. > > > > > > > > > > Hi Gavin > > > > Could you please kindly create a folder for Apache HttpComponents? > > > > Cheers > > > > Oleg > > > > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Andreas, On Fri, Jul 17, 2020 at 2:10 PM Andreas Lehmkühler wrote: > Hi Gav, > > please create a folder for PDFBox. > Done. > > Thanks ! > > Regards > Andreas > > 16.07.2020 18:33:23 Gavin McDonald : > > > Hi All, > > > > This NOTICE is for everyone on builds.apache.org. We are migrating to a > new > > Cloudbees based Client Master called https://ci-builds.apache.org. The > > migrations of all jobs needs to be done before the switch off date of > 15th > > August 2020, so you have a maximum of 4 weeks. > > > > There is no tool or automated way of migrating your jobs, the > > differences in the platforms, the plugins and the setup makes it > impossible > > to do in a safe way. So, you all need to start creating new jobs on > > ci-infra.a.o and then , when you are happy, turn off your old builds on > > builds.a.o. > > > > There are currently 4 agents over there ready to take jobs, plus a > floating > > agent which is shared amongst many masters (more to come). I will migrate > > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > > will keep an eye of load across both and adjust accordingly. > > > > If needed, create a ticket on INFRA jira for any issues that crop up, or > > email here on builds@a.o. there may be one or two plugins we need to > > install/tweak etc. > > > > We will be not using 'Views' at the top level, but rather we will take > > advantage of 'Folders Plus' - each project will get its own Folder and > have > > authorisation access to create/edit jobs etc within that folder. I will > > create these folders as you ask for them to start with. This setup allows > > for credentials isolation amongst other benefits, including but not > limited > > to exclusive agents (Controlled Agents) for your own use , should you > have > > any project targeted donations of agents. > > > > As with other aspects of the ASF, projects can choose to just enable all > > committers access to their folder, just ask. > > > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will > not > > be setting up any forwarding rules or anything like that. > > > > So, please, get started *now *on this so you can be sure we are all > > completed before the final cutoff date of 15th August 2020. > > > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > > tickets. > > > > Hadoop and related projects have their own migration path to follow, same > > cut off date, Cassandra, Beam, CouchDB have already migrated and are > doing > > very well in their new homes. > > > > Lets get going ... > > > > -- > > > > *Gavin McDonald* > > Systems Administrator > > ASF Infrastructure Team > > > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Stefan, On Fri, Jul 17, 2020 at 6:20 PM Stefan Bodewig wrote: > Hi Gavin > > please add a folder for Ant - access for all committers. > > Done. > Right now there seem to be no executors running Windows or am I > overlooking something? I assume they will be added later. > There are 2 configured as 'floating agents' meaning they are available for ci-builds and all the other project specific masters we have. Use the 'Windows' label. More will be added over the next few days > > Stefan > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Sebb On Fri, Jul 17, 2020 at 2:10 PM sebb wrote: > Please create Commons > Added ,please test. -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Oleg On Fri, Jul 17, 2020 at 1:41 PM Oleg Kalnichevski wrote: > > Hi Gavin > > Could you please kindly create a folder for Apache HttpComponents? > Done > > Cheers > > Oleg > > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Gav, can you create a Creadur as well with the right to create jobs for all PMC-members? I filed https://issues.apache.org/jira/browse/INFRA-20535 as well. Thanks / cheers, Phil
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Lukasz On Fri, Jul 17, 2020 at 1:08 PM Lukasz Lenart wrote: > No idea why but "cleanWs" [1] is missing [2] > We install the recommended set of Plugins to start with. Part of this exercise of moving over includes finding out what other plugins need to be installed in addition. Now installed > > [1] https://www.jenkins.io/doc/pipeline/steps/ws-cleanup/ > [2] > https://ci-builds.apache.org/job/Struts/job/Struts%20Core/job/master/1/console > > > Regards > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.pl/ > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Lukasz On Fri, Jul 17, 2020 at 1:03 PM Lukasz Lenart wrote: > Is is possible to add this plugin > https://plugins.jenkins.io/basic-branch-build-strategies/ Done. > > > Thanks a lot! > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.pl/ > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Vladimir On Fri, Jul 17, 2020 at 12:48 PM Vladimir Sitnikov < sitnikov.vladi...@gmail.com> wrote: > Gavin, please create folders for Calcite and JMeter. > Please make it so committers can view/edit jobs. > All done! > > Vladimir > > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Gavin please add a folder for Ant - access for all committers. Right now there seem to be no executors running Windows or am I overlooking something? I assume they will be added later. Stefan
RE: [IMPORTANT] - Migration to ci-builds.a.o
Hi, Would it be possible to create NetBeans folder. Access to commiters. Regards Eric -Message d'origine- De : sebb Envoyé : vendredi 17 juillet 2020 14:11 À : builds Cc : Gav Objet : Re: [IMPORTANT] - Migration to ci-builds.a.o Please create Commons On Fri, 17 Jul 2020 at 12:41, Oleg Kalnichevski wrote: > > On Thu, 2020-07-16 at 22:25 +0100, sebb wrote: > > On Thu, 16 Jul 2020 at 17:33, Gavin McDonald > > wrote: > > > > > > Hi All, > > > > > > This NOTICE is for everyone on builds.apache.org. We are migrating > > > to a new Cloudbees based Client Master called > > > https://ci-builds.apache.org. > > > The > > > migrations of all jobs needs to be done before the switch off date > > > of 15th August 2020, so you have a maximum of 4 weeks. > > > > > > There is no tool or automated way of migrating your jobs, the > > > differences in the platforms, the plugins and the setup makes it > > > impossible to do in a safe way. So, you all need to start creating > > > new jobs on ci-infra.a.o and then , when you are happy, turn off > > > your old builds on builds.a.o. > > > > > > Hi Gavin > > Could you please kindly create a folder for Apache HttpComponents? > > Cheers > > Oleg >
Re: [IMPORTANT] - Migration to ci-builds.a.o
Please create Commons On Fri, 17 Jul 2020 at 12:41, Oleg Kalnichevski wrote: > > On Thu, 2020-07-16 at 22:25 +0100, sebb wrote: > > On Thu, 16 Jul 2020 at 17:33, Gavin McDonald > > wrote: > > > > > > Hi All, > > > > > > This NOTICE is for everyone on builds.apache.org. We are migrating > > > to a new > > > Cloudbees based Client Master called https://ci-builds.apache.org. > > > The > > > migrations of all jobs needs to be done before the switch off date > > > of 15th > > > August 2020, so you have a maximum of 4 weeks. > > > > > > There is no tool or automated way of migrating your jobs, the > > > differences in the platforms, the plugins and the setup makes it > > > impossible > > > to do in a safe way. So, you all need to start creating new jobs on > > > ci-infra.a.o and then , when you are happy, turn off your old > > > builds on > > > builds.a.o. > > > > > > Hi Gavin > > Could you please kindly create a folder for Apache HttpComponents? > > Cheers > > Oleg >
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Gav, please create a folder for PDFBox. Thanks ! Regards Andreas 16.07.2020 18:33:23 Gavin McDonald : > Hi All, > > This NOTICE is for everyone on builds.apache.org. We are migrating to a new > Cloudbees based Client Master called https://ci-builds.apache.org. The > migrations of all jobs needs to be done before the switch off date of 15th > August 2020, so you have a maximum of 4 weeks. > > There is no tool or automated way of migrating your jobs, the > differences in the platforms, the plugins and the setup makes it impossible > to do in a safe way. So, you all need to start creating new jobs on > ci-infra.a.o and then , when you are happy, turn off your old builds on > builds.a.o. > > There are currently 4 agents over there ready to take jobs, plus a floating > agent which is shared amongst many masters (more to come). I will migrate > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > will keep an eye of load across both and adjust accordingly. > > If needed, create a ticket on INFRA jira for any issues that crop up, or > email here on builds@a.o. there may be one or two plugins we need to > install/tweak etc. > > We will be not using 'Views' at the top level, but rather we will take > advantage of 'Folders Plus' - each project will get its own Folder and have > authorisation access to create/edit jobs etc within that folder. I will > create these folders as you ask for them to start with. This setup allows > for credentials isolation amongst other benefits, including but not limited > to exclusive agents (Controlled Agents) for your own use , should you have > any project targeted donations of agents. > > As with other aspects of the ASF, projects can choose to just enable all > committers access to their folder, just ask. > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will not > be setting up any forwarding rules or anything like that. > > So, please, get started *now *on this so you can be sure we are all > completed before the final cutoff date of 15th August 2020. > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > tickets. > > Hadoop and related projects have their own migration path to follow, same > cut off date, Cassandra, Beam, CouchDB have already migrated and are doing > very well in their new homes. > > Lets get going ... > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team >
Re: [IMPORTANT] - Migration to ci-builds.a.o
On Thu, 2020-07-16 at 22:25 +0100, sebb wrote: > On Thu, 16 Jul 2020 at 17:33, Gavin McDonald > wrote: > > > > Hi All, > > > > This NOTICE is for everyone on builds.apache.org. We are migrating > > to a new > > Cloudbees based Client Master called https://ci-builds.apache.org. > > The > > migrations of all jobs needs to be done before the switch off date > > of 15th > > August 2020, so you have a maximum of 4 weeks. > > > > There is no tool or automated way of migrating your jobs, the > > differences in the platforms, the plugins and the setup makes it > > impossible > > to do in a safe way. So, you all need to start creating new jobs on > > ci-infra.a.o and then , when you are happy, turn off your old > > builds on > > builds.a.o. > > Hi Gavin Could you please kindly create a folder for Apache HttpComponents? Cheers Oleg
Re: [IMPORTANT] - Migration to ci-builds.a.o
No idea why but "cleanWs" [1] is missing [2] [1] https://www.jenkins.io/doc/pipeline/steps/ws-cleanup/ [2] https://ci-builds.apache.org/job/Struts/job/Struts%20Core/job/master/1/console Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/
Re: [IMPORTANT] - Migration to ci-builds.a.o
Is is possible to add this plugin https://plugins.jenkins.io/basic-branch-build-strategies/ Thanks a lot! -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/
Re: [IMPORTANT] - Migration to ci-builds.a.o
pt., 17 lip 2020 o 11:58 Gavin McDonald napisał(a): > > > On Fri, Jul 17, 2020 at 7:33 AM Lukasz Lenart > wrote: > >> pt., 17 lip 2020 o 07:31 Lukasz Lenart >> napisał(a): >> > Please create a folder for Struts, same as here - or should I create a >> ticket? >> > https://builds.apache.org/view/S-Z/view/Struts/ > > > Created. > > https://ci-builds.apache.org/job/Struts/ > Thanks! > And also I don't see any option to create a job >> > > Cart before the Horse :) - the Folder with auth for struts committers > needs to be there > before you can create jobs within that Folder. > Here https://issues.apache.org/jira/browse/INFRA-20532 but as far as I see I can create jobs, thanks! Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/
Re: [IMPORTANT] - Migration to ci-builds.a.o
Gavin, please create folders for Calcite and JMeter. Please make it so committers can view/edit jobs. Vladimir
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Sebb On Thu, Jul 16, 2020 at 11:25 PM sebb wrote: > > > What are the differences between the platforms and the plugins? > There are quite a lot of differences. Each jobs config would need adjusting manually to suit the new system, its plugins versions, the lack of views and the inclusion of Folders and its Auth strategy. The ci-builds main page points to > https://cwiki.apache.org/confluence/display/INFRA/Jenkins which > appears to document the old system > Yes I'll get a new page up soon. > > Is there no way to take config.xml from the old host and adjust it for > the new host? > If you want to do that for your project(s) feel free to have a try, I can provide the config, just tell me which project. I imagine then you would want to know what the adjusted config should look like? When you say 'take config.xml' and adjust it for the new host, it sounds so easy, but I'll tell you now that there is one for each job - that is there are *1759 config.xml* files. so yeah I am not going to go through each and every one of them trying to adjust them for the new system. I suspect most projects can just recreate their jobs just fine in the UI, or if needed I will supply them their config.xml files, with no guarantees that their tweaks will work. This is also an opportunity to remove old cruft that has been building up on Jenkins since 2008. Many jobs are disabled and won't need migrating. Many jobs are failing and have been for months if not longer, and so the project will notice this when migrating their jobs over. The current jobs folder is 2.4TB in size and so this is an opportunity to start again on this also. I have not just been lazy in deciding not to try and migrate all jobs, there are very good reasons for me not to do so. So please don't think I am passing the buck here, its the best way forward is to have every project involved in the moving of their own jobs.' > > There are currently 4 agents over there ready to take jobs, plus a > floating > > agent which is shared amongst many masters (more to come). I will migrate > > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > > will keep an eye of load across both and adjust accordingly. > > > > If needed, create a ticket on INFRA jira for any issues that crop up, or > > email here on builds@a.o. there may be one or two plugins we need to > > install/tweak etc. > > > > We will be not using 'Views' at the top level, but rather we will take > > advantage of 'Folders Plus' - each project will get its own Folder and > have > > authorisation access to create/edit jobs etc within that folder. I will > > create these folders as you ask for them to start with. This setup allows > > for credentials isolation amongst other benefits, including but not > limited > > to exclusive agents (Controlled Agents) for your own use , should you > have > > any project targeted donations of agents. > > > > As with other aspects of the ASF, projects can choose to just enable all > > committers access to their folder, just ask. > > > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will > not > > be setting up any forwarding rules or anything like that. > > > > So, please, get started *now *on this so you can be sure we are all > > completed before the final cutoff date of 15th August 2020. > > > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > > tickets. > > > > Hadoop and related projects have their own migration path to follow, same > > cut off date, Cassandra, Beam, CouchDB have already migrated and are > doing > > very well in their new homes. > > > > Lets get going ... > > > > -- > > > > *Gavin McDonald* > > Systems Administrator > > ASF Infrastructure Team > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Matt On Thu, Jul 16, 2020 at 11:33 PM Matt Sicker wrote: > Oh, I misread the initial email. Could you create a folder for Logging? > > Done. > On Thu, 16 Jul 2020 at 16:31, Matt Sicker wrote: > > > > I tried logging in, but I don't seem to have any ability to create > anything. > Now that you have a Logging folder, that should be fixed. > > > > On Thu, 16 Jul 2020 at 11:33, Gavin McDonald > wrote: > > > > > > Hi All, > > > > > > This NOTICE is for everyone on builds.apache.org. We are migrating to > a new > > > Cloudbees based Client Master called https://ci-builds.apache.org. The > > > migrations of all jobs needs to be done before the switch off date of > 15th > > > August 2020, so you have a maximum of 4 weeks. > > > > > > There is no tool or automated way of migrating your jobs, the > > > differences in the platforms, the plugins and the setup makes it > impossible > > > to do in a safe way. So, you all need to start creating new jobs on > > > ci-infra.a.o and then , when you are happy, turn off your old builds on > > > builds.a.o. > > > > > > There are currently 4 agents over there ready to take jobs, plus a > floating > > > agent which is shared amongst many masters (more to come). I will > migrate > > > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > > > will keep an eye of load across both and adjust accordingly. > > > > > > If needed, create a ticket on INFRA jira for any issues that crop up, > or > > > email here on builds@a.o. there may be one or two plugins we need to > > > install/tweak etc. > > > > > > We will be not using 'Views' at the top level, but rather we will take > > > advantage of 'Folders Plus' - each project will get its own Folder and > have > > > authorisation access to create/edit jobs etc within that folder. I will > > > create these folders as you ask for them to start with. This setup > allows > > > for credentials isolation amongst other benefits, including but not > limited > > > to exclusive agents (Controlled Agents) for your own use , should you > have > > > any project targeted donations of agents. > > > > > > As with other aspects of the ASF, projects can choose to just enable > all > > > committers access to their folder, just ask. > > > > > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will > not > > > be setting up any forwarding rules or anything like that. > > > > > > So, please, get started *now *on this so you can be sure we are all > > > completed before the final cutoff date of 15th August 2020. > > > > > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > > > tickets. > > > > > > Hadoop and related projects have their own migration path to follow, > same > > > cut off date, Cassandra, Beam, CouchDB have already migrated and are > doing > > > very well in their new homes. > > > > > > Lets get going ... > > > > > > -- > > > > > > *Gavin McDonald* > > > Systems Administrator > > > ASF Infrastructure Team > > > > > > > > -- > > Matt Sicker > > > > -- > Matt Sicker > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
HI Matt On Thu, Jul 16, 2020 at 11:38 PM Matt Sicker wrote: > Couple plugin requests, though they both require a newer version of > Jenkins: > > * > https://docs.cloudbees.com/docs/cloudbees-ci/latest/slack-integration/setting-up-psm > * > https://docs.cloudbees.com/docs/cloudbees-ci/latest/scm-integration/enabling-scm-reporting Yep that is fine. We are due another upgrade - we do them every 3 months and the last one was April, so I'll get that done on the Operations Center and all 6 Client Masters over the next few days. > > On Thu, 16 Jul 2020 at 16:32, Matt Sicker wrote: > > > > Oh, I misread the initial email. Could you create a folder for Logging? > > > > On Thu, 16 Jul 2020 at 16:31, Matt Sicker wrote: > > > > > > I tried logging in, but I don't seem to have any ability to create > anything. > > > > > > On Thu, 16 Jul 2020 at 11:33, Gavin McDonald > wrote: > > > > > > > > Hi All, > > > > > > > > This NOTICE is for everyone on builds.apache.org. We are migrating > to a new > > > > Cloudbees based Client Master called https://ci-builds.apache.org. > The > > > > migrations of all jobs needs to be done before the switch off date > of 15th > > > > August 2020, so you have a maximum of 4 weeks. > > > > > > > > There is no tool or automated way of migrating your jobs, the > > > > differences in the platforms, the plugins and the setup makes it > impossible > > > > to do in a safe way. So, you all need to start creating new jobs on > > > > ci-infra.a.o and then , when you are happy, turn off your old builds > on > > > > builds.a.o. > > > > > > > > There are currently 4 agents over there ready to take jobs, plus a > floating > > > > agent which is shared amongst many masters (more to come). I will > migrate > > > > away 2 more agents from builds.a.o to ci-builds.a.o every few days, > and > > > > will keep an eye of load across both and adjust accordingly. > > > > > > > > If needed, create a ticket on INFRA jira for any issues that crop > up, or > > > > email here on builds@a.o. there may be one or two plugins we need to > > > > install/tweak etc. > > > > > > > > We will be not using 'Views' at the top level, but rather we will > take > > > > advantage of 'Folders Plus' - each project will get its own Folder > and have > > > > authorisation access to create/edit jobs etc within that folder. I > will > > > > create these folders as you ask for them to start with. This setup > allows > > > > for credentials isolation amongst other benefits, including but not > limited > > > > to exclusive agents (Controlled Agents) for your own use , should > you have > > > > any project targeted donations of agents. > > > > > > > > As with other aspects of the ASF, projects can choose to just enable > all > > > > committers access to their folder, just ask. > > > > > > > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but > will not > > > > be setting up any forwarding rules or anything like that. > > > > > > > > So, please, get started *now *on this so you can be sure we are all > > > > completed before the final cutoff date of 15th August 2020. > > > > > > > > Any questions - I expect a few (dozen :) ) - ask away and/or file > INFRA > > > > tickets. > > > > > > > > Hadoop and related projects have their own migration path to follow, > same > > > > cut off date, Cassandra, Beam, CouchDB have already migrated and are > doing > > > > very well in their new homes. > > > > > > > > Lets get going ... > > > > > > > > -- > > > > > > > > *Gavin McDonald* > > > > Systems Administrator > > > > ASF Infrastructure Team > > > > > > > > > > > > -- > > > Matt Sicker > > > > > > > > -- > > Matt Sicker > > > > -- > Matt Sicker > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi Uwe On Fri, Jul 17, 2020 at 10:08 AM Uwe Schindler wrote: > Hi Gav, > > In addition to Sebb's comments: Would it still be possible to get the > job.xml files on old server? When I personally migrate Jenkins or Plugins, > its easier to take the xml files, do some regex replace or remove stuff and > then upoad them on new system. > Yes, that is fine, any project that wants their jobs 'config.xml' file to tweak is welcome to do so. I'm just saying that I won't be doing that. There is no way to automate this. > Creating the jobs with the UI is kind of ... horrible. > It would certainly also be horrible if all jobs were left to me, hence passing this along as the project's responsibility. > > In addition for Apache Lucene: We have 2 private nodes, according to your > mail, we can now make them fully private to our "folder", right? (nodes > "lucene" and "lucene2"). We would open an issue to coordinate, inlcuding > slack. I tend to think that we first migrate one of the slave nodes to new > system, setup jobs and test. Once all is running we move the other node. > They can be restricted to builds only from your Folder yes. > > Is there a list of plugins? I hope the important stuff like - email-ext, > tool-environment (that's the two most important for us) - are available. > Those two are already installed, yes. I don't have a list of plugins yet available but I will create a page over the next day or so. > > Uwe > > - > Uwe Schindler > uschind...@apache.org > ASF Member, Apache Lucene PMC / Committer > Bremen, Germany > https://lucene.apache.org/ > > > -Original Message- > > From: sebb > > Sent: Thursday, July 16, 2020 11:26 PM > > To: builds ; Gav > > Subject: Re: [IMPORTANT] - Migration to ci-builds.a.o > > > > On Thu, 16 Jul 2020 at 17:33, Gavin McDonald > > wrote: > > > > > > Hi All, > > > > > > This NOTICE is for everyone on builds.apache.org. We are migrating to > a new > > > Cloudbees based Client Master called https://ci-builds.apache.org. The > > > migrations of all jobs needs to be done before the switch off date of > 15th > > > August 2020, so you have a maximum of 4 weeks. > > > > > > There is no tool or automated way of migrating your jobs, the > > > differences in the platforms, the plugins and the setup makes it > impossible > > > to do in a safe way. So, you all need to start creating new jobs on > > > ci-infra.a.o and then , when you are happy, turn off your old builds on > > > builds.a.o. > > > > What are the differences between the platforms and the plugins? > > The ci-builds main page points to > > https://cwiki.apache.org/confluence/display/INFRA/Jenkins which > > appears to document the old system > > > > Is there no way to take config.xml from the old host and adjust it for > > the new host? > > > > > There are currently 4 agents over there ready to take jobs, plus a > floating > > > agent which is shared amongst many masters (more to come). I will > migrate > > > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > > > will keep an eye of load across both and adjust accordingly. > > > > > > If needed, create a ticket on INFRA jira for any issues that crop up, > or > > > email here on builds@a.o. there may be one or two plugins we need to > > > install/tweak etc. > > > > > > We will be not using 'Views' at the top level, but rather we will take > > > advantage of 'Folders Plus' - each project will get its own Folder and > have > > > authorisation access to create/edit jobs etc within that folder. I will > > > create these folders as you ask for them to start with. This setup > allows > > > for credentials isolation amongst other benefits, including but not > limited > > > to exclusive agents (Controlled Agents) for your own use , should you > have > > > any project targeted donations of agents. > > > > > > As with other aspects of the ASF, projects can choose to just enable > all > > > committers access to their folder, just ask. > > > > > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will > not > > > be setting up any forwarding rules or anything like that. > > > > > > So, please, get started *now *on this so you can be sure we are all > > > completed before the final cutoff date of 15th August 2020. > > > > > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > > > tickets. > > > > > > Hadoop and related projects have their own migration path to follow, > same > > > cut off date, Cassandra, Beam, CouchDB have already migrated and are > doing > > > very well in their new homes. > > > > > > Lets get going ... > > > > > > -- > > > > > > *Gavin McDonald* > > > Systems Administrator > > > ASF Infrastructure Team > > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
On Fri, Jul 17, 2020 at 7:33 AM Lukasz Lenart wrote: > pt., 17 lip 2020 o 07:31 Lukasz Lenart > napisał(a): > > Please create a folder for Struts, same as here - or should I create a > ticket? > > https://builds.apache.org/view/S-Z/view/Struts/ Created. https://ci-builds.apache.org/job/Struts/ > > > And also I don't see any option to create a job > Cart before the Horse :) - the Folder with auth for struts committers needs to be there before you can create jobs within that Folder. > > > Regards > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.pl/ > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
RE: [IMPORTANT] - Migration to ci-builds.a.o
Hi Gav, In addition to Sebb's comments: Would it still be possible to get the job.xml files on old server? When I personally migrate Jenkins or Plugins, its easier to take the xml files, do some regex replace or remove stuff and then upoad them on new system. Creating the jobs with the UI is kind of ... horrible. In addition for Apache Lucene: We have 2 private nodes, according to your mail, we can now make them fully private to our "folder", right? (nodes "lucene" and "lucene2"). We would open an issue to coordinate, inlcuding slack. I tend to think that we first migrate one of the slave nodes to new system, setup jobs and test. Once all is running we move the other node. Is there a list of plugins? I hope the important stuff like - email-ext, tool-environment (that's the two most important for us) - are available. Uwe - Uwe Schindler uschind...@apache.org ASF Member, Apache Lucene PMC / Committer Bremen, Germany https://lucene.apache.org/ > -Original Message- > From: sebb > Sent: Thursday, July 16, 2020 11:26 PM > To: builds ; Gav > Subject: Re: [IMPORTANT] - Migration to ci-builds.a.o > > On Thu, 16 Jul 2020 at 17:33, Gavin McDonald > wrote: > > > > Hi All, > > > > This NOTICE is for everyone on builds.apache.org. We are migrating to a new > > Cloudbees based Client Master called https://ci-builds.apache.org. The > > migrations of all jobs needs to be done before the switch off date of 15th > > August 2020, so you have a maximum of 4 weeks. > > > > There is no tool or automated way of migrating your jobs, the > > differences in the platforms, the plugins and the setup makes it impossible > > to do in a safe way. So, you all need to start creating new jobs on > > ci-infra.a.o and then , when you are happy, turn off your old builds on > > builds.a.o. > > What are the differences between the platforms and the plugins? > The ci-builds main page points to > https://cwiki.apache.org/confluence/display/INFRA/Jenkins which > appears to document the old system > > Is there no way to take config.xml from the old host and adjust it for > the new host? > > > There are currently 4 agents over there ready to take jobs, plus a floating > > agent which is shared amongst many masters (more to come). I will migrate > > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > > will keep an eye of load across both and adjust accordingly. > > > > If needed, create a ticket on INFRA jira for any issues that crop up, or > > email here on builds@a.o. there may be one or two plugins we need to > > install/tweak etc. > > > > We will be not using 'Views' at the top level, but rather we will take > > advantage of 'Folders Plus' - each project will get its own Folder and have > > authorisation access to create/edit jobs etc within that folder. I will > > create these folders as you ask for them to start with. This setup allows > > for credentials isolation amongst other benefits, including but not limited > > to exclusive agents (Controlled Agents) for your own use , should you have > > any project targeted donations of agents. > > > > As with other aspects of the ASF, projects can choose to just enable all > > committers access to their folder, just ask. > > > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will not > > be setting up any forwarding rules or anything like that. > > > > So, please, get started *now *on this so you can be sure we are all > > completed before the final cutoff date of 15th August 2020. > > > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > > tickets. > > > > Hadoop and related projects have their own migration path to follow, same > > cut off date, Cassandra, Beam, CouchDB have already migrated and are doing > > very well in their new homes. > > > > Lets get going ... > > > > -- > > > > *Gavin McDonald* > > Systems Administrator > > ASF Infrastructure Team
Re: [IMPORTANT] - Migration to ci-builds.a.o
pt., 17 lip 2020 o 07:31 Lukasz Lenart napisał(a): > Please create a folder for Struts, same as here - or should I create a ticket? > https://builds.apache.org/view/S-Z/view/Struts/ And also I don't see any option to create a job Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/
Re: [IMPORTANT] - Migration to ci-builds.a.o
Hi, Please create a folder for Struts, same as here - or should I create a ticket? https://builds.apache.org/view/S-Z/view/Struts/ Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/
Re: [IMPORTANT] - Migration to ci-builds.a.o
Couple plugin requests, though they both require a newer version of Jenkins: * https://docs.cloudbees.com/docs/cloudbees-ci/latest/slack-integration/setting-up-psm * https://docs.cloudbees.com/docs/cloudbees-ci/latest/scm-integration/enabling-scm-reporting On Thu, 16 Jul 2020 at 16:32, Matt Sicker wrote: > > Oh, I misread the initial email. Could you create a folder for Logging? > > On Thu, 16 Jul 2020 at 16:31, Matt Sicker wrote: > > > > I tried logging in, but I don't seem to have any ability to create anything. > > > > On Thu, 16 Jul 2020 at 11:33, Gavin McDonald wrote: > > > > > > Hi All, > > > > > > This NOTICE is for everyone on builds.apache.org. We are migrating to a > > > new > > > Cloudbees based Client Master called https://ci-builds.apache.org. The > > > migrations of all jobs needs to be done before the switch off date of 15th > > > August 2020, so you have a maximum of 4 weeks. > > > > > > There is no tool or automated way of migrating your jobs, the > > > differences in the platforms, the plugins and the setup makes it > > > impossible > > > to do in a safe way. So, you all need to start creating new jobs on > > > ci-infra.a.o and then , when you are happy, turn off your old builds on > > > builds.a.o. > > > > > > There are currently 4 agents over there ready to take jobs, plus a > > > floating > > > agent which is shared amongst many masters (more to come). I will migrate > > > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > > > will keep an eye of load across both and adjust accordingly. > > > > > > If needed, create a ticket on INFRA jira for any issues that crop up, or > > > email here on builds@a.o. there may be one or two plugins we need to > > > install/tweak etc. > > > > > > We will be not using 'Views' at the top level, but rather we will take > > > advantage of 'Folders Plus' - each project will get its own Folder and > > > have > > > authorisation access to create/edit jobs etc within that folder. I will > > > create these folders as you ask for them to start with. This setup allows > > > for credentials isolation amongst other benefits, including but not > > > limited > > > to exclusive agents (Controlled Agents) for your own use , should you have > > > any project targeted donations of agents. > > > > > > As with other aspects of the ASF, projects can choose to just enable all > > > committers access to their folder, just ask. > > > > > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will not > > > be setting up any forwarding rules or anything like that. > > > > > > So, please, get started *now *on this so you can be sure we are all > > > completed before the final cutoff date of 15th August 2020. > > > > > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > > > tickets. > > > > > > Hadoop and related projects have their own migration path to follow, same > > > cut off date, Cassandra, Beam, CouchDB have already migrated and are doing > > > very well in their new homes. > > > > > > Lets get going ... > > > > > > -- > > > > > > *Gavin McDonald* > > > Systems Administrator > > > ASF Infrastructure Team > > > > > > > > -- > > Matt Sicker > > > > -- > Matt Sicker -- Matt Sicker
Re: [IMPORTANT] - Migration to ci-builds.a.o
Oh, I misread the initial email. Could you create a folder for Logging? On Thu, 16 Jul 2020 at 16:31, Matt Sicker wrote: > > I tried logging in, but I don't seem to have any ability to create anything. > > On Thu, 16 Jul 2020 at 11:33, Gavin McDonald wrote: > > > > Hi All, > > > > This NOTICE is for everyone on builds.apache.org. We are migrating to a new > > Cloudbees based Client Master called https://ci-builds.apache.org. The > > migrations of all jobs needs to be done before the switch off date of 15th > > August 2020, so you have a maximum of 4 weeks. > > > > There is no tool or automated way of migrating your jobs, the > > differences in the platforms, the plugins and the setup makes it impossible > > to do in a safe way. So, you all need to start creating new jobs on > > ci-infra.a.o and then , when you are happy, turn off your old builds on > > builds.a.o. > > > > There are currently 4 agents over there ready to take jobs, plus a floating > > agent which is shared amongst many masters (more to come). I will migrate > > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > > will keep an eye of load across both and adjust accordingly. > > > > If needed, create a ticket on INFRA jira for any issues that crop up, or > > email here on builds@a.o. there may be one or two plugins we need to > > install/tweak etc. > > > > We will be not using 'Views' at the top level, but rather we will take > > advantage of 'Folders Plus' - each project will get its own Folder and have > > authorisation access to create/edit jobs etc within that folder. I will > > create these folders as you ask for them to start with. This setup allows > > for credentials isolation amongst other benefits, including but not limited > > to exclusive agents (Controlled Agents) for your own use , should you have > > any project targeted donations of agents. > > > > As with other aspects of the ASF, projects can choose to just enable all > > committers access to their folder, just ask. > > > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will not > > be setting up any forwarding rules or anything like that. > > > > So, please, get started *now *on this so you can be sure we are all > > completed before the final cutoff date of 15th August 2020. > > > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > > tickets. > > > > Hadoop and related projects have their own migration path to follow, same > > cut off date, Cassandra, Beam, CouchDB have already migrated and are doing > > very well in their new homes. > > > > Lets get going ... > > > > -- > > > > *Gavin McDonald* > > Systems Administrator > > ASF Infrastructure Team > > > > -- > Matt Sicker -- Matt Sicker
Re: [IMPORTANT] - Migration to ci-builds.a.o
I tried logging in, but I don't seem to have any ability to create anything. On Thu, 16 Jul 2020 at 11:33, Gavin McDonald wrote: > > Hi All, > > This NOTICE is for everyone on builds.apache.org. We are migrating to a new > Cloudbees based Client Master called https://ci-builds.apache.org. The > migrations of all jobs needs to be done before the switch off date of 15th > August 2020, so you have a maximum of 4 weeks. > > There is no tool or automated way of migrating your jobs, the > differences in the platforms, the plugins and the setup makes it impossible > to do in a safe way. So, you all need to start creating new jobs on > ci-infra.a.o and then , when you are happy, turn off your old builds on > builds.a.o. > > There are currently 4 agents over there ready to take jobs, plus a floating > agent which is shared amongst many masters (more to come). I will migrate > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > will keep an eye of load across both and adjust accordingly. > > If needed, create a ticket on INFRA jira for any issues that crop up, or > email here on builds@a.o. there may be one or two plugins we need to > install/tweak etc. > > We will be not using 'Views' at the top level, but rather we will take > advantage of 'Folders Plus' - each project will get its own Folder and have > authorisation access to create/edit jobs etc within that folder. I will > create these folders as you ask for them to start with. This setup allows > for credentials isolation amongst other benefits, including but not limited > to exclusive agents (Controlled Agents) for your own use , should you have > any project targeted donations of agents. > > As with other aspects of the ASF, projects can choose to just enable all > committers access to their folder, just ask. > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will not > be setting up any forwarding rules or anything like that. > > So, please, get started *now *on this so you can be sure we are all > completed before the final cutoff date of 15th August 2020. > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > tickets. > > Hadoop and related projects have their own migration path to follow, same > cut off date, Cassandra, Beam, CouchDB have already migrated and are doing > very well in their new homes. > > Lets get going ... > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team -- Matt Sicker
Re: [IMPORTANT] - Migration to ci-builds.a.o
On Thu, 16 Jul 2020 at 17:33, Gavin McDonald wrote: > > Hi All, > > This NOTICE is for everyone on builds.apache.org. We are migrating to a new > Cloudbees based Client Master called https://ci-builds.apache.org. The > migrations of all jobs needs to be done before the switch off date of 15th > August 2020, so you have a maximum of 4 weeks. > > There is no tool or automated way of migrating your jobs, the > differences in the platforms, the plugins and the setup makes it impossible > to do in a safe way. So, you all need to start creating new jobs on > ci-infra.a.o and then , when you are happy, turn off your old builds on > builds.a.o. What are the differences between the platforms and the plugins? The ci-builds main page points to https://cwiki.apache.org/confluence/display/INFRA/Jenkins which appears to document the old system Is there no way to take config.xml from the old host and adjust it for the new host? > There are currently 4 agents over there ready to take jobs, plus a floating > agent which is shared amongst many masters (more to come). I will migrate > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > will keep an eye of load across both and adjust accordingly. > > If needed, create a ticket on INFRA jira for any issues that crop up, or > email here on builds@a.o. there may be one or two plugins we need to > install/tweak etc. > > We will be not using 'Views' at the top level, but rather we will take > advantage of 'Folders Plus' - each project will get its own Folder and have > authorisation access to create/edit jobs etc within that folder. I will > create these folders as you ask for them to start with. This setup allows > for credentials isolation amongst other benefits, including but not limited > to exclusive agents (Controlled Agents) for your own use , should you have > any project targeted donations of agents. > > As with other aspects of the ASF, projects can choose to just enable all > committers access to their folder, just ask. > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will not > be setting up any forwarding rules or anything like that. > > So, please, get started *now *on this so you can be sure we are all > completed before the final cutoff date of 15th August 2020. > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > tickets. > > Hadoop and related projects have their own migration path to follow, same > cut off date, Cassandra, Beam, CouchDB have already migrated and are doing > very well in their new homes. > > Lets get going ... > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team
