You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@pulsar.apache.org by Dave Fisher <wa...@apache.org> on 2020/08/14 19:48:05 UTC

Fwd: [IMPORTANT] - Migration to ci-builds.a.o

Hi -

There is a critical migration for Jenkins builds that the project is missing.

Several PMC members ought to be subscribed to builds@apache.org.

Please act quickly.

Regards,
Dave

> Begin forwarded message:
> 
> From: Gavin McDonald <gm...@apache.org>
> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> Date: July 16, 2020 at 9:33:08 AM PDT
> To: builds <bu...@apache.org>
> Reply-To: builds@apache.org
> Reply-To: gmcdonald@apache.org
> 
> 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

Posted by Hiroyuki Sakai <hs...@yahoo-corp.jp>.

Hi,


The GitHub PR trigger isn't working yet, but the migration is complete.

(Now trying to fix the GitHub trigger.)

https://ci-builds.apache.org/job/Pulsar/job/pulsar_precommit_client_node/


Regards,
Hiroyuki Sakai


________________________________
From: Nozomi Kurihara <nk...@yahoo-corp.jp>
Sent: Thursday, August 20, 2020 13:55
To: Dev <de...@pulsar.apache.org>
Subject: Re: [IMPORTANT] - Migration to ci-builds.a.o

Hi Sijie,

Thank you for your advice.

> Maybe it is worth moving to Github Actions.

Yes, we're planning to migrate to Github Actions.

However, I think we should first migrate from builds.a.o to ci-builds.a.o as soon as possible since the deadline was over.

After that, we try to promote the migration to Github Actions.

Best Regards,
Nozomi

********************
Nozomi Kurihara

Cloud Platform Development Division
System Management Group

Yahoo Japan Corporation
Kioi Tower, Tokyo Garden Terrace Kioicho,
1-3 Kioicho, Chiyoda-ku, Tokyo, 102-8282 Japan

TEL +81-3-6898-5866
nkurihar@yahoo-corp.jp
********************

________________________________
差出人: Sijie Guo <gu...@gmail.com>
送信日時: 2020年8月20日 1:42
宛先: Dev <de...@pulsar.apache.org>
件名: Re: [IMPORTANT] - Migration to ci-builds.a.o

Nozomi,

Thank you for chiming in here! I forgot that the pulsar-client-node is
still using Jenkins. Maybe it is worth moving to Github Actions. Thoughts?

- Sijie

On Tue, Aug 18, 2020 at 6:45 PM Nozomi Kurihara <nk...@yahoo-corp.jp>
wrote:

> Hi Dave,
>
> Thank you for notifying.
>
> I'm sorry for missing the migration announcement ...
>
> Unfortunately pulsar_precommit_client_node is still using Jenkins and
> we're trying to migrate it soon.
>
> Regards,
> Nozomi
> ________________________________
> 差出人: Dave Fisher <wa...@apache.org>
> 送信日時: 2020年8月19日 3:37
> 宛先: dev@pulsar.apache.org <de...@pulsar.apache.org>
> 件名: Re: [IMPORTANT] - Migration to ci-builds.a.o
>
> Hi -
>
> Infra has created a folder in case it is needed for one of those
> “projects”.
>
> https://ci-builds.apache.org/job/Pulsar/
>
> Let me know if any more help is needed.
>
> Regards,
> Dave
>
> > On Aug 18, 2020, at 11:15 AM, Sijie Guo <gu...@gmail.com> wrote:
> >
> > Okay. We can look into it to see if we can just delete them.
> >
> >
> > - Sijie
> >
> > On Tue, Aug 18, 2020 at 11:52 AM Dave Fisher <wa...@apache.org> wrote:
> >
> >> Hi Sijie,
> >>
> >> They are still running on builds.apahce.org.
> >>
> >> Regards,
> >> Dave
> >>
> >>> On Aug 18, 2020, at 10:50 AM, Sijie Guo <gu...@gmail.com> wrote:
> >>>
> >>> Hi Dave,
> >>>
> >>> I believe all the Pulsar projects have migrated to use Github Actions
> for
> >>> CI. The jobs might already not be used anymore. Other committers can
> >>> confirm if that is the case.
> >>>
> >>> - Sijie
> >>>
> >>>
> >>> On Tue, Aug 18, 2020 at 11:39 AM Dave Fisher <wa...@apache.org> wrote:
> >>>
> >>>> Hi -
> >>>>
> >>>> It is critical to complete this migration THIS WEEK.
> >>>>
> >>>> I’ve submitted https://issues.apache.org/jira/browse/INFRA-20720 to
> >>>> request the folder.
> >>>>
> >>>> Pulsar has the following “projects” on builds.a.o.
> >>>>
> >>>> pulsar-manager-build
> >>>> pulsar-master
> >>>> pulsar-pull-request-c++-test
> >>>> pulsar-release-binaries
> >>>> pulsar-website-build
> >>>> pulsar_precommit_client_node
> >>>> pulsar_release_nightly_snapshot
> >>>>
> >>>> I can migrate the projects so that are not lost, but I have no idea
> >> about
> >>>> the integrations with GitHub and any missing Jenkins Plugins.
> >>>>
> >>>> These all need to be migrated by Friday EOD.
> >>>>
> >>>> Regards,
> >>>> Dave
> >>>>
> >>>>
> >>>>> On Aug 14, 2020, at 1:35 PM, Dave Fisher <wa...@apache.org> wrote:
> >>>>>
> >>>>> Migration technique:
> >>>>
> >>
> https://cwiki.apache.org/confluence/display/INFRA/Migrating+jobs+from+Jenkins+to+Cloudbees
> >>>>>
> >>>>> Helpful info:
> >>>>
> >>
> https://cwiki.apache.org/confluence/display/INFRA/Kicking+off+a+Jenkins+build+with+a+GitHub+PR
> >>>>>
> >>>>>
> >>>>>> On Aug 14, 2020, at 12:48 PM, Dave Fisher <wa...@apache.org> wrote:
> >>>>>>
> >>>>>> Hi -
> >>>>>>
> >>>>>> There is a critical migration for Jenkins builds that the project is
> >>>> missing.
> >>>>>>
> >>>>>> Several PMC members ought to be subscribed to builds@apache.org.
> >>>>>>
> >>>>>> Please act quickly.
> >>>>>>
> >>>>>> Regards,
> >>>>>> Dave
> >>>>>>
> >>>>>>> Begin forwarded message:
> >>>>>>>
> >>>>>>> From: Gavin McDonald <gm...@apache.org>
> >>>>>>> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> >>>>>>> Date: July 16, 2020 at 9:33:08 AM PDT
> >>>>>>> To: builds <bu...@apache.org>
> >>>>>>> Reply-To: builds@apache.org
> >>>>>>> Reply-To: gmcdonald@apache.org
> >>>>>>>
> >>>>>>> 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

Posted by Nozomi Kurihara <nk...@yahoo-corp.jp>.

Hi Sijie,

Thank you for your advice.

> Maybe it is worth moving to Github Actions.

Yes, we're planning to migrate to Github Actions.

However, I think we should first migrate from builds.a.o to ci-builds.a.o as soon as possible since the deadline was over.

After that, we try to promote the migration to Github Actions.

Best Regards,
Nozomi

********************
Nozomi Kurihara

Cloud Platform Development Division
System Management Group

Yahoo Japan Corporation
Kioi Tower, Tokyo Garden Terrace Kioicho,
1-3 Kioicho, Chiyoda-ku, Tokyo, 102-8282 Japan

TEL +81-3-6898-5866
nkurihar@yahoo-corp.jp
********************

________________________________
差出人: Sijie Guo <gu...@gmail.com>
送信日時: 2020年8月20日 1:42
宛先: Dev <de...@pulsar.apache.org>
件名: Re: [IMPORTANT] - Migration to ci-builds.a.o

Nozomi,

Thank you for chiming in here! I forgot that the pulsar-client-node is
still using Jenkins. Maybe it is worth moving to Github Actions. Thoughts?

- Sijie

On Tue, Aug 18, 2020 at 6:45 PM Nozomi Kurihara <nk...@yahoo-corp.jp>
wrote:

> Hi Dave,
>
> Thank you for notifying.
>
> I'm sorry for missing the migration announcement ...
>
> Unfortunately pulsar_precommit_client_node is still using Jenkins and
> we're trying to migrate it soon.
>
> Regards,
> Nozomi
> ________________________________
> 差出人: Dave Fisher <wa...@apache.org>
> 送信日時: 2020年8月19日 3:37
> 宛先: dev@pulsar.apache.org <de...@pulsar.apache.org>
> 件名: Re: [IMPORTANT] - Migration to ci-builds.a.o
>
> Hi -
>
> Infra has created a folder in case it is needed for one of those
> “projects”.
>
> https://ci-builds.apache.org/job/Pulsar/
>
> Let me know if any more help is needed.
>
> Regards,
> Dave
>
> > On Aug 18, 2020, at 11:15 AM, Sijie Guo <gu...@gmail.com> wrote:
> >
> > Okay. We can look into it to see if we can just delete them.
> >
> >
> > - Sijie
> >
> > On Tue, Aug 18, 2020 at 11:52 AM Dave Fisher <wa...@apache.org> wrote:
> >
> >> Hi Sijie,
> >>
> >> They are still running on builds.apahce.org.
> >>
> >> Regards,
> >> Dave
> >>
> >>> On Aug 18, 2020, at 10:50 AM, Sijie Guo <gu...@gmail.com> wrote:
> >>>
> >>> Hi Dave,
> >>>
> >>> I believe all the Pulsar projects have migrated to use Github Actions
> for
> >>> CI. The jobs might already not be used anymore. Other committers can
> >>> confirm if that is the case.
> >>>
> >>> - Sijie
> >>>
> >>>
> >>> On Tue, Aug 18, 2020 at 11:39 AM Dave Fisher <wa...@apache.org> wrote:
> >>>
> >>>> Hi -
> >>>>
> >>>> It is critical to complete this migration THIS WEEK.
> >>>>
> >>>> I’ve submitted https://issues.apache.org/jira/browse/INFRA-20720 to
> >>>> request the folder.
> >>>>
> >>>> Pulsar has the following “projects” on builds.a.o.
> >>>>
> >>>> pulsar-manager-build
> >>>> pulsar-master
> >>>> pulsar-pull-request-c++-test
> >>>> pulsar-release-binaries
> >>>> pulsar-website-build
> >>>> pulsar_precommit_client_node
> >>>> pulsar_release_nightly_snapshot
> >>>>
> >>>> I can migrate the projects so that are not lost, but I have no idea
> >> about
> >>>> the integrations with GitHub and any missing Jenkins Plugins.
> >>>>
> >>>> These all need to be migrated by Friday EOD.
> >>>>
> >>>> Regards,
> >>>> Dave
> >>>>
> >>>>
> >>>>> On Aug 14, 2020, at 1:35 PM, Dave Fisher <wa...@apache.org> wrote:
> >>>>>
> >>>>> Migration technique:
> >>>>
> >>
> https://cwiki.apache.org/confluence/display/INFRA/Migrating+jobs+from+Jenkins+to+Cloudbees
> >>>>>
> >>>>> Helpful info:
> >>>>
> >>
> https://cwiki.apache.org/confluence/display/INFRA/Kicking+off+a+Jenkins+build+with+a+GitHub+PR
> >>>>>
> >>>>>
> >>>>>> On Aug 14, 2020, at 12:48 PM, Dave Fisher <wa...@apache.org> wrote:
> >>>>>>
> >>>>>> Hi -
> >>>>>>
> >>>>>> There is a critical migration for Jenkins builds that the project is
> >>>> missing.
> >>>>>>
> >>>>>> Several PMC members ought to be subscribed to builds@apache.org.
> >>>>>>
> >>>>>> Please act quickly.
> >>>>>>
> >>>>>> Regards,
> >>>>>> Dave
> >>>>>>
> >>>>>>> Begin forwarded message:
> >>>>>>>
> >>>>>>> From: Gavin McDonald <gm...@apache.org>
> >>>>>>> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> >>>>>>> Date: July 16, 2020 at 9:33:08 AM PDT
> >>>>>>> To: builds <bu...@apache.org>
> >>>>>>> Reply-To: builds@apache.org
> >>>>>>> Reply-To: gmcdonald@apache.org
> >>>>>>>
> >>>>>>> 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

Posted by Sijie Guo <gu...@gmail.com>.

Nozomi,

Thank you for chiming in here! I forgot that the pulsar-client-node is
still using Jenkins. Maybe it is worth moving to Github Actions. Thoughts?

- Sijie

On Tue, Aug 18, 2020 at 6:45 PM Nozomi Kurihara <nk...@yahoo-corp.jp>
wrote:

> Hi Dave,
>
> Thank you for notifying.
>
> I'm sorry for missing the migration announcement ...
>
> Unfortunately pulsar_precommit_client_node is still using Jenkins and
> we're trying to migrate it soon.
>
> Regards,
> Nozomi
> ________________________________
> 差出人: Dave Fisher <wa...@apache.org>
> 送信日時: 2020年8月19日 3:37
> 宛先: dev@pulsar.apache.org <de...@pulsar.apache.org>
> 件名: Re: [IMPORTANT] - Migration to ci-builds.a.o
>
> Hi -
>
> Infra has created a folder in case it is needed for one of those
> “projects”.
>
> https://ci-builds.apache.org/job/Pulsar/
>
> Let me know if any more help is needed.
>
> Regards,
> Dave
>
> > On Aug 18, 2020, at 11:15 AM, Sijie Guo <gu...@gmail.com> wrote:
> >
> > Okay. We can look into it to see if we can just delete them.
> >
> >
> > - Sijie
> >
> > On Tue, Aug 18, 2020 at 11:52 AM Dave Fisher <wa...@apache.org> wrote:
> >
> >> Hi Sijie,
> >>
> >> They are still running on builds.apahce.org.
> >>
> >> Regards,
> >> Dave
> >>
> >>> On Aug 18, 2020, at 10:50 AM, Sijie Guo <gu...@gmail.com> wrote:
> >>>
> >>> Hi Dave,
> >>>
> >>> I believe all the Pulsar projects have migrated to use Github Actions
> for
> >>> CI. The jobs might already not be used anymore. Other committers can
> >>> confirm if that is the case.
> >>>
> >>> - Sijie
> >>>
> >>>
> >>> On Tue, Aug 18, 2020 at 11:39 AM Dave Fisher <wa...@apache.org> wrote:
> >>>
> >>>> Hi -
> >>>>
> >>>> It is critical to complete this migration THIS WEEK.
> >>>>
> >>>> I’ve submitted https://issues.apache.org/jira/browse/INFRA-20720 to
> >>>> request the folder.
> >>>>
> >>>> Pulsar has the following “projects” on builds.a.o.
> >>>>
> >>>> pulsar-manager-build
> >>>> pulsar-master
> >>>> pulsar-pull-request-c++-test
> >>>> pulsar-release-binaries
> >>>> pulsar-website-build
> >>>> pulsar_precommit_client_node
> >>>> pulsar_release_nightly_snapshot
> >>>>
> >>>> I can migrate the projects so that are not lost, but I have no idea
> >> about
> >>>> the integrations with GitHub and any missing Jenkins Plugins.
> >>>>
> >>>> These all need to be migrated by Friday EOD.
> >>>>
> >>>> Regards,
> >>>> Dave
> >>>>
> >>>>
> >>>>> On Aug 14, 2020, at 1:35 PM, Dave Fisher <wa...@apache.org> wrote:
> >>>>>
> >>>>> Migration technique:
> >>>>
> >>
> https://cwiki.apache.org/confluence/display/INFRA/Migrating+jobs+from+Jenkins+to+Cloudbees
> >>>>>
> >>>>> Helpful info:
> >>>>
> >>
> https://cwiki.apache.org/confluence/display/INFRA/Kicking+off+a+Jenkins+build+with+a+GitHub+PR
> >>>>>
> >>>>>
> >>>>>> On Aug 14, 2020, at 12:48 PM, Dave Fisher <wa...@apache.org> wrote:
> >>>>>>
> >>>>>> Hi -
> >>>>>>
> >>>>>> There is a critical migration for Jenkins builds that the project is
> >>>> missing.
> >>>>>>
> >>>>>> Several PMC members ought to be subscribed to builds@apache.org.
> >>>>>>
> >>>>>> Please act quickly.
> >>>>>>
> >>>>>> Regards,
> >>>>>> Dave
> >>>>>>
> >>>>>>> Begin forwarded message:
> >>>>>>>
> >>>>>>> From: Gavin McDonald <gm...@apache.org>
> >>>>>>> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> >>>>>>> Date: July 16, 2020 at 9:33:08 AM PDT
> >>>>>>> To: builds <bu...@apache.org>
> >>>>>>> Reply-To: builds@apache.org
> >>>>>>> Reply-To: gmcdonald@apache.org
> >>>>>>>
> >>>>>>> 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
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>
> >>
>
>