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

Posted to builds@apache.org by Gavin McDonald <gm...@apache.org> on 2020/07/16 16:33:08 UTC

[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

Posted by Konrad Windszus <kw...@apache.org>.

Hi Gavin, can you create a folder for Sling with edit rights for all Sling committers?

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
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>
> >>
>
>

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

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

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 Dave Fisher <wa...@apache.org>.

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>.

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 Dave Fisher <wa...@apache.org>.

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>.

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 Dave Fisher <wa...@apache.org>.

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 Dave Fisher <wa...@apache.org>.

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 Dave Fisher <wa...@apache.org>.

Your folder is ready.

Regards,
Dave

> On Aug 17, 2020, at 8:19 PM, Brennan Ashton <ba...@brennanashton.com> wrote:
> 
> Dave,
> Our INFRA ticket is still waiting so I cannot migrate the job. 
> 
> https://issues.apache.org/jira/browse/INFRA-20687 <https://issues.apache.org/jira/browse/INFRA-20687>
> 
> Thanks,
> Brennan
> 
> On Fri, Aug 14, 2020, 1:27 PM Dave Fisher <wave@apache.org <ma...@apache.org>> wrote:
> You will find this page helpful: https://cwiki.apache.org/confluence/display/INFRA/Migrating+jobs+from+Jenkins+to+Cloudbees <https://cwiki.apache.org/confluence/display/INFRA/Migrating+jobs+from+Jenkins+to+Cloudbees>
> 
> > On Aug 14, 2020, at 1:02 PM, Brennan Ashton <bashton@brennanashton.com <ma...@brennanashton.com>> wrote:
> > 
> > Dave,
> > Thanks for the heads up.  We did not know about this (I'll subscribe
> > to the build list), it looks like we need to file a ticket for a new
> > folder to be created for the project (NuttX).  I'll do that now and
> > try to migrate tonight.
> > 
> > Thanks
> > --Brennan
> > 
> > On Fri, Aug 14, 2020 at 12:49 PM Dave Fisher <wave@apache.org <ma...@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 <ma...@apache.org>.
> >> 
> >> Please act quickly.
> >> 
> >> Regards,
> >> Dave
> >> 
> >>> Begin forwarded message:
> >>> 
> >>> From: Gavin McDonald <gmcdonald@apache.org <ma...@apache.org>>
> >>> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> >>> Date: July 16, 2020 at 9:33:08 AM PDT
> >>> To: builds <builds@apache.org <ma...@apache.org>>
> >>> Reply-To: builds@apache.org <ma...@apache.org>
> >>> Reply-To: gmcdonald@apache.org <ma...@apache.org>
> >>> 
> >>> Hi All,
> >>> 
> >>> This NOTICE is for everyone on builds.apache.org <http://builds.apache.org/>. We are migrating to a new
> >>> Cloudbees based Client Master called https://ci-builds.apache.org <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 <http://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 Brennan Ashton <ba...@brennanashton.com>.

Dave,
Our INFRA ticket is still waiting so I cannot migrate the job.

https://issues.apache.org/jira/browse/INFRA-20687

Thanks,
Brennan

On Fri, Aug 14, 2020, 1:27 PM Dave Fisher <wa...@apache.org> wrote:

> You will find this page helpful:
> https://cwiki.apache.org/confluence/display/INFRA/Migrating+jobs+from+Jenkins+to+Cloudbees
>
> > On Aug 14, 2020, at 1:02 PM, Brennan Ashton <ba...@brennanashton.com>
> wrote:
> >
> > Dave,
> > Thanks for the heads up.  We did not know about this (I'll subscribe
> > to the build list), it looks like we need to file a ticket for a new
> > folder to be created for the project (NuttX).  I'll do that now and
> > try to migrate tonight.
> >
> > Thanks
> > --Brennan
> >
> > On Fri, Aug 14, 2020 at 12:49 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 Dave Fisher <wa...@apache.org>.

You will find this page helpful: https://cwiki.apache.org/confluence/display/INFRA/Migrating+jobs+from+Jenkins+to+Cloudbees

> On Aug 14, 2020, at 1:02 PM, Brennan Ashton <ba...@brennanashton.com> wrote:
> 
> Dave,
> Thanks for the heads up.  We did not know about this (I'll subscribe
> to the build list), it looks like we need to file a ticket for a new
> folder to be created for the project (NuttX).  I'll do that now and
> try to migrate tonight.
> 
> Thanks
> --Brennan
> 
> On Fri, Aug 14, 2020 at 12:49 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 Brennan Ashton <ba...@brennanashton.com>.

Dave,
Thanks for the heads up.  We did not know about this (I'll subscribe
to the build list), it looks like we need to file a ticket for a new
folder to be created for the project (NuttX).  I'll do that now and
try to migrate tonight.

Thanks
--Brennan

On Fri, Aug 14, 2020 at 12:49 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: Fwd: [IMPORTANT] - Migration to ci-builds.a.o

Posted by "P. Ottlinger" <po...@apache.org>.

Hi Dave,

thanks for reaching out - as Tamaya is about to retire I decided not to
do anything.

Cheers & happy weekend

Phil

Am 14.08.20 um 21:48 schrieb Dave Fisher:
> 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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tuweni.apache.org
For additional commands, e-mail: dev-help@tuweni.apache.org

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

Posted by "P. Ottlinger" <po...@apache.org>.

Hi Dave,

thanks for reaching out - as Tamaya is about to retire I decided not to
do anything.

Cheers & happy weekend

Phil

Am 14.08.20 um 21:48 schrieb Dave Fisher:
> 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

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

Posted by "P. Ottlinger" <po...@apache.org>.

Hi Dave,

thanks for reaching out - as Tamaya is about to retire I decided not to
do anything.

Cheers & happy weekend

Phil

Am 14.08.20 um 21:48 schrieb Dave Fisher:
> 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

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

Posted by "P. Ottlinger" <po...@apache.org>.

Hi Dave,

thanks for reaching out - as Tamaya is about to retire I decided not to
do anything.

Cheers & happy weekend

Phil

Am 14.08.20 um 21:48 schrieb Dave Fisher:
> 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

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

Posted by "P. Ottlinger" <po...@apache.org>.

Hi Dave,

thanks for reaching out - as Tamaya is about to retire I decided not to
do anything.

Cheers & happy weekend

Phil

Am 14.08.20 um 21:48 schrieb Dave Fisher:
> 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

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

Posted by Dave Fisher <wa...@apache.org>.

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 Gavin McDonald <gm...@apache.org>.

Hi Chris,

On Sun, Jul 19, 2020 at 2:02 PM Christofer Dutz <ch...@c-ware.de>
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" <ch...@c-ware.de>:
>
>     Hi,
>
>     could you please create the folder for the Apache PLC4X project?
>
>     Thanks,
>
>     Chris
>
>     Am 18.07.20, 20:04 schrieb "Stefan Seelmann" <mail@stefan-seelmann.de
> >:
>
>         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 <
> mail@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

Posted by Christofer Dutz <ch...@c-ware.de>.

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" <ch...@c-ware.de>:

    Hi,

    could you please create the folder for the Apache PLC4X project?

    Thanks,

    Chris

    Am 18.07.20, 20:04 schrieb "Stefan Seelmann" <ma...@stefan-seelmann.de>:

        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 <ma...@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/
        >>
        > 
        >

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

Posted by Christofer Dutz <ch...@c-ware.de>.

Hi,

could you please create the folder for the Apache PLC4X project?

Thanks,

Chris

Am 18.07.20, 20:04 schrieb "Stefan Seelmann" <ma...@stefan-seelmann.de>:

    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 <ma...@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/
    >>
    > 
    >

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

Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.

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 <ma...@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/
>>
> 
>

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

Posted by Gavin McDonald <gm...@apache.org>.

Thanks Stefan,

Can you create an INFRA jira ticket for this one please.

On Sat, Jul 18, 2020 at 5:48 PM Stefan Seelmann <ma...@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

Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.

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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Stefan,

On Fri, Jul 17, 2020 at 6:20 PM Stefan Bodewig <bo...@apache.org> 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

Posted by Stefan Bodewig <bo...@apache.org>.

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

Posted by Josh Fischer <jo...@joshfischer.io>.

Thanks for moving them Huijun.

- Josh

On Mon, Jul 20, 2020 at 7:11 PM H W <hu...@gmail.com> wrote:

> All the jobs have been moved to https://ci-builds.apache.org/job/Heron/
>
> On Sun, Jul 19, 2020 at 5:18 PM H W <hu...@gmail.com> wrote:
>
> > Jira for creating a folder in the new ci-builds.
> > https://issues.apache.org/jira/browse/INFRA-20551
> > Once the folder is done, we can start putting the jobs to the new home.
> > The current jobs. https://builds.apache.org/view/Heron/. Total 9 jobs: 5
> > jobs for building release, 2 for daily integration test, 2 for
> doc/website
> >
> > On Sun, Jul 19, 2020 at 3:45 PM Josh Fischer <jo...@joshfischer.io>
> wrote:
> >
> >> This came across builds@.  We need to work to migrate all of our
> jenkins
> >> jobs to the new instance.  Looks  like the final cut off date is Aug 15,
> >> 2020.
> >>
> >> ---------- Forwarded message ---------
> >> From: Gavin McDonald <gm...@apache.org>
> >> Date: Thu, Jul 16, 2020 at 11:33 AM
> >> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> >> To: builds <bu...@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 H W <hu...@gmail.com>.

All the jobs have been moved to https://ci-builds.apache.org/job/Heron/

On Sun, Jul 19, 2020 at 5:18 PM H W <hu...@gmail.com> wrote:

> Jira for creating a folder in the new ci-builds.
> https://issues.apache.org/jira/browse/INFRA-20551
> Once the folder is done, we can start putting the jobs to the new home.
> The current jobs. https://builds.apache.org/view/Heron/. Total 9 jobs: 5
> jobs for building release, 2 for daily integration test, 2 for doc/website
>
> On Sun, Jul 19, 2020 at 3:45 PM Josh Fischer <jo...@joshfischer.io> wrote:
>
>> This came across builds@.  We need to work to migrate all of our jenkins
>> jobs to the new instance.  Looks  like the final cut off date is Aug 15,
>> 2020.
>>
>> ---------- Forwarded message ---------
>> From: Gavin McDonald <gm...@apache.org>
>> Date: Thu, Jul 16, 2020 at 11:33 AM
>> Subject: [IMPORTANT] - Migration to ci-builds.a.o
>> To: builds <bu...@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 H W <hu...@gmail.com>.

Jira for creating a folder in the new ci-builds.
https://issues.apache.org/jira/browse/INFRA-20551
Once the folder is done, we can start putting the jobs to the new home.
The current jobs. https://builds.apache.org/view/Heron/. Total 9 jobs: 5
jobs for building release, 2 for daily integration test, 2 for doc/website

On Sun, Jul 19, 2020 at 3:45 PM Josh Fischer <jo...@joshfischer.io> wrote:

> This came across builds@.  We need to work to migrate all of our jenkins
> jobs to the new instance.  Looks  like the final cut off date is Aug 15,
> 2020.
>
> ---------- Forwarded message ---------
> From: Gavin McDonald <gm...@apache.org>
> Date: Thu, Jul 16, 2020 at 11:33 AM
> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> To: builds <bu...@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
>

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

Posted by Josh Fischer <jo...@joshfischer.io>.

This came across builds@.  We need to work to migrate all of our jenkins
jobs to the new instance.  Looks  like the final cut off date is Aug 15,
2020.

---------- Forwarded message ---------
From: Gavin McDonald <gm...@apache.org>
Date: Thu, Jul 16, 2020 at 11:33 AM
Subject: [IMPORTANT] - Migration to ci-builds.a.o
To: builds <bu...@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

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

Posted by "Aaron D. Mihalik" <aa...@gmail.com>.

Is there anyone (ie a committer) available to look into this transition. We
need to look at this soon.

I set up the initial builds, so I’m available to help. But I would like to
increase awareness about the build environment in the group

Here’s a full thread:

https://www.mail-archive.com/builds@apache.org/msg07142.html

—Aaron

---------- Forwarded message ---------
From: Gavin McDonald <gm...@apache.org>
Date: Thu, Jul 16, 2020 at 12:33 PM
Subject: [IMPORTANT] - Migration to ci-builds.a.o
To: builds <bu...@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: Fwd: [IMPORTANT] - Migration to ci-builds.a.o / new target folder for all creadur projects

Posted by "P. Ottlinger" <po...@apache.org>.

Am 17.07.20 um 13:36 schrieb P. Ottlinger:
> Hi,
> 
> I filed
> https://issues.apache.org/jira/browse/INFRA-20535
> to create a new Creadur infrastructure and will start migrating our
> build jobs over to the new environment.


A basic build/CI setup is done for all Creadur projects:
https://ci-builds.apache.org/job/Creadur/

Have a great weekend,

Phil

Fwd: [IMPORTANT] - Migration to ci-builds.a.o / new target folder for all creadur projects

Posted by "P. Ottlinger" <po...@apache.org>.

Hi,

I filed
https://issues.apache.org/jira/browse/INFRA-20535
to create a new Creadur infrastructure and will start migrating our
build jobs over to the new environment.

Just fyi

Cheers,
Phil


-------- Weitergeleitete Nachricht --------
Betreff: [IMPORTANT] - Migration to ci-builds.a.o
Datum: Thu, 16 Jul 2020 18:33:08 +0200
Von: Gavin McDonald <gm...@apache.org>
Antwort an: builds@apache.org, gmcdonald@apache.org
An: builds <bu...@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 Gavin McDonald <gm...@apache.org>.

Hi Stefan,

On Sat, Jul 18, 2020 at 7:42 AM Stefan Seelmann <ma...@stefan-seelmann.de>
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

Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.

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

Posted by Davyd McColl <da...@gmail.com>.

Please let me know if I can help with that - if you're using the new build 
process I made and something doesn't work as expected, I'm happy to help.


On July 18, 2020 02:58:03 Matt Sicker <bo...@gmail.com> wrote:

> I've finished migrating all our jobs that I could find. There's a
> log4net pipeline that I could potentially enable in the new CI, but
> the Windows node doesn't seem to be working quite yet.
>
> On Thu, 16 Jul 2020 at 12:36, Matt Sicker <bo...@gmail.com> wrote:
>>
>> Here’s the answer to my previous forward. I can look into this to make sure 
>> our builds are good there.
>>
>> ---------- Forwarded message ---------
>> From: Gavin McDonald <gm...@apache.org>
>> Date: Thu, Jul 16, 2020 at 11:33
>> Subject: [IMPORTANT] - Migration to ci-builds.a.o
>> To: builds <bu...@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
>> --
>> Matt Sicker <bo...@gmail.com>
>
>
>
> -- 
> Matt Sicker <bo...@gmail.com>

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

Posted by Matt Sicker <bo...@gmail.com>.

I've finished migrating all our jobs that I could find. There's a
log4net pipeline that I could potentially enable in the new CI, but
the Windows node doesn't seem to be working quite yet.

On Thu, 16 Jul 2020 at 12:36, Matt Sicker <bo...@gmail.com> wrote:
>
> Here’s the answer to my previous forward. I can look into this to make sure our builds are good there.
>
> ---------- Forwarded message ---------
> From: Gavin McDonald <gm...@apache.org>
> Date: Thu, Jul 16, 2020 at 11:33
> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> To: builds <bu...@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
> --
> Matt Sicker <bo...@gmail.com>



-- 
Matt Sicker <bo...@gmail.com>

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

Posted by Matt Sicker <bo...@gmail.com>.

Here’s the answer to my previous forward. I can look into this to make sure
our builds are good there.

---------- Forwarded message ---------
From: Gavin McDonald <gm...@apache.org>
Date: Thu, Jul 16, 2020 at 11:33
Subject: [IMPORTANT] - Migration to ci-builds.a.o
To: builds <bu...@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
-- 
Matt Sicker <bo...@gmail.com>

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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Andreas,

On Fri, Jul 17, 2020 at 2:10 PM Andreas Lehmkühler <an...@lehmi.de> wrote:

> Hi Gav,
>
> please create a folder for PDFBox.
>

Done.


>
> Thanks !
>
> Regards
> Andreas
>
> 16.07.2020 18:33:23 Gavin McDonald <gm...@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
> >
>


-- 

*Gavin McDonald*
Systems Administrator
ASF Infrastructure Team

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

Posted by Andreas Lehmkühler <an...@lehmi.de>.

Hi Gav,

please create a folder for PDFBox.

Thanks !

Regards
Andreas

16.07.2020 18:33:23 Gavin McDonald <gm...@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
>

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

Posted by Uwe Schindler <uw...@thetaphi.de>.

Hi all,

ASF is moving Jenkins to a new infrastructure @
https://ci-builds.apache.org. We have to move our stuff on our own and --
unfortunately create new jobs - migration is not possible. I can slowly do
this. Steve and I also have to negotiate when the two lucene slave nodes are
moved to new infrastructure. Most nodes will be moved automatically, but our
private ones should be negotiated. I will ask on Slack how to proceed.

See attached mail for more information!

Uwe

-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: uwe@thetaphi.de

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

Posted by Andy Seaborne <an...@apache.org>.

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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Mike,

On Sat, Jul 18, 2020 at 12:50 AM Mike Jumper <mj...@apache.org> 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

Posted by Mike Jumper <mj...@apache.org>.

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 <gm...@apache.org> 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
>

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

Posted by Dave Fisher <wa...@apache.org>.

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

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

Posted by Dave Fisher <wa...@apache.org>.

Hi -

This migration has been completed for the Incubator clutch analysis and site build.

It’s crunch time now. Some podlings have managed to move their builds, but others have not.

(1) Request a Folder for your project from Infra. We are no longer putting podling builds in the Incubator folder.
(2) There is a script to move build ”projects”.
	https://cwiki.apache.org/confluence/display/INFRA/Migrating+jobs+from+Jenkins+to+Cloudbees
(3) Request missing plugins from Infra on builds@a.o mailing list.
(4) Fix any GitHub credential issues.

Ask for help.

Start yesterday!

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 Piotr Zarzycki <pi...@apache.org>.

Thanks Gavin! Wonderful. I look forward :) 

On 2020/08/07 08:43:05, Gavin McDonald <gm...@apache.org> wrote: 
> Hi Piotr,
> 
> On Fri, Aug 7, 2020 at 10:10 AM Piotr Zarzycki <pi...@apache.org> 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 <gm...@apache.org> 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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Piotr,

On Fri, Aug 7, 2020 at 10:10 AM Piotr Zarzycki <pi...@apache.org> 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 <gm...@apache.org> 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

Posted by Piotr Zarzycki <pi...@apache.org>.

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 <gm...@apache.org> 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

Posted by Andor Molnar <an...@apache.org>.

Answering myself:

Flaky Test Report



> On 2020. Aug 14., at 12:52, Andor Molnar <an...@apache.org> wrote:
> 
> Hi devs,
> 
> There’s some movement from Apache on Jenkins migration. Github account is now available on the new instance which will be useful for PreCommit builds. I started the tests.
> 
> Deadline (15 Aug) is approaching. Is there anything else which has fallen through the cracks and has to be migrated to the new instance?
> 
> Andor
> 
> 
> 
>> On 2020. Jul 24., at 19:15, Patrick Hunt <ph...@apache.org> wrote:
>> 
>> On Fri, Jul 24, 2020 at 3:05 AM Andor Molnar <an...@apache.org> wrote:
>> 
>>> Hi,
>>> 
>>> Jenkinsfile is now committed to master, 3.5 and 3.6 branches. Build is
>>> running here:
>>> 
>>> https://ci-hadoop.apache.org/view/ZooKeeper/job/zookeeper-master-maven-multipipeline/
>>> 
>>> I use standard Git interface to access the repo, because using GitHub
>>> means that branch discovery has to run through the github API. The problem
>>> with this is that I haven’t specified credentials and anonymous access is
>>> limited by some quota, meaning the discovery process takes ages (1-2 hours).
>>> 
>>> Builds are running fine except I see a lot of concurrent builds on master
>>> without any meaningful SCM change. Odd. I will change pollSCM trigger to
>>> run @hourly and will see how it goes.
>>> 
>>> What’s outstanding?
>>> 
>>> - JDKs: currently only two: 8, 11 (LTS versions). What other JDKs would
>>> you like to run against?
>>> 
>>> - GitHub Pull Requests precommit job: I have no idea how to do this, but I
>>> suspect we have to use the GitHub Api for this to work.
>>> 
>>> 
>> Not sure if this is helpful but I saw it recently:
>> 
>>> we need ability to trigger builds on pull request creation/updates which
>> 
>>> requires the plug-in below or similar:
>> 
>>> https://plugins.jenkins.io/ghprb/
>> 
>> 
>> 
>> That plugin is deprecated and not recommended for use .
>> 
>> 
>> I have installed the *branch source plugin instead*, hopefully that works
>> for
>> 
>> you.
>> 
>> 
>> If not, let's investigate further what else we can do
>> 
>> 
>> 
>>> - Windows build: there’s no Windows agent available currently in the new
>>> instance.
>>> 
>>> - Ant builds: do we need this?
>>> 
>>> Please share your thoughts.
>>> 
>>> Regards,
>>> Andor
>>> 
>>> 
>>> 
>>> 
>>>> On 2020. Jul 23., at 22:08, Andor Molnar <an...@apache.org> wrote:
>>>> 
>>>> Hi folks,
>>>> 
>>>> PR is available: https://github.com/apache/zookeeper/pull/1409
>>>> 
>>>> Andor
>>>> 
>>>> 
>>>> 
>>>> On Thu, 2020-07-23 at 11:32 +0200, Andor Molnar wrote:
>>>>> Created a Jira for the task:
>>>>> 
>>>>> https://issues.apache.org/jira/browse/ZOOKEEPER-3896
>>>>> 
>>>>> Andor
>>>>> 
>>>>> 
>>>>> 
>>>>>> On 2020. Jul 21., at 12:10, Andor Molnar <an...@apache.org> wrote:
>>>>>> 
>>>>>> Where’s that example…?
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>> On 2020. Jul 20., at 20:02, Enrico Olivelli <eo...@gmail.com>
>>>>>>> wrote:
>>>>>>> 
>>>>>>> Il Lun 20 Lug 2020, 19:40 Andor Molnar <an...@apache.org> ha
>>>>>>> scritto:
>>>>>>> 
>>>>>>>> Hi Enrico,
>>>>>>>> 
>>>>>>>> No worries, I only created a few jobs to make some progress,
>>>>>>>> but feel free
>>>>>>>> to ignore that and do it in a better way. The “View” or
>>>>>>>> “Folder” that I was
>>>>>>>> adding jobs is
>>>>>>>> 
>>>>>>>> https://ci-hadoop.apache.org/view/ZooKeeper/
>>>>>>>> 
>>>>>>>> 
>>>>>>>> Andor
>>>>>>>> 
>>>>>>> 
>>>>>>> This is an example from Apache Maven  project. It is very complex
>>>>>>> because
>>>>>>> tests are in another repo and for lots if other reasons. We just
>>>>>>> have to
>>>>>>> create a simpler file.
>>>>>>> 
>>>>>>> If nobody volunteers I can try to spend some time but I won't
>>>>>>> have a fast
>>>>>>> pace these weeks
>>>>>>> 
>>>>>>> 
>>>>>>> Enrico
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>>> 
>>>>>>>>> On 2020. Jul 20., at 19:34, Enrico Olivelli <
>>>>>>>>> eolivelli@gmail.com> wrote:
>>>>>>>>> 
>>>>>>>>> Il Lun 20 Lug 2020, 19:02 Patrick Hunt <ph...@apache.org> ha
>>>>>>>>> scritto:
>>>>>>>>> 
>>>>>>>>>> On Mon, Jul 20, 2020 at 9:47 AM Enrico Olivelli <
>>>>>>>>>> eolivelli@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>>> Il Lun 20 Lug 2020, 18:41 Patrick Hunt <ph...@apache.org>
>>>>>>>>>>> ha scritto:
>>>>>>>>>>> 
>>>>>>>>>>>> On Sat, Jul 18, 2020 at 12:20 PM Andor Molnar <
>>>>>>>>>>>> andor@apache.org>
>>>>>>>>>> wrote:
>>>>>>>>>>>>> Hi Pat,
>>>>>>>>>>>>> 
>>>>>>>>>>>>> I have admin rights in the new system too and
>>>>>>>>>>>>> probably can work on
>>>>>>>>>> this
>>>>>>>>>>>> on
>>>>>>>>>>>>> Monday.
>>>>>>>>>>>>> What’s “matrix” config? Shouldn’t we just replicate
>>>>>>>>>>>>> the same jobs on
>>>>>>>>>>> the
>>>>>>>>>>>>> new instance?
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>> Not sure on the exact name/feature but "matrix" is
>>>>>>>>>>>> basically the
>>>>>>>>>> ability
>>>>>>>>>>> to
>>>>>>>>>>>> say "run this build/test across a set of JDK versions"
>>>>>>>>>>>> rather than a
>>>>>>>>>>> single
>>>>>>>>>>>> version. As a result, instead of 3 jobs for zk3.6.0,
>>>>>>>>>>>> jdk 1/2/3 you end
>>>>>>>>>> up
>>>>>>>>>>>> with a single job which runs three times, one for each
>>>>>>>>>>>> jdk type and
>>>>>>>>>>>> summarizes the results. I've seen this before, I assume
>>>>>>>>>>>> it's a feature
>>>>>>>>>> of
>>>>>>>>>>>> jenkins itself?
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> We should use Jenkins files and this configuration will
>>>>>>>>>>> be easy and
>>>>>>>>>>> committed to git
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> The ability to do "gitops" would be amazing!
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Yes.
>>>>>>>>> But I saw on Slack that Andor already started to create new
>>>>>>>>> jobs.
>>>>>>>>> We should do only one way in order not to waste time.
>>>>>>>>> 
>>>>>>>>> Andor can you please share your work?
>>>>>>>>> Thanks for doing it
>>>>>>>>> 
>>>>>>>>> Enrico
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> Patrick
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>>> Enrico
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>>> Patrick
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>>> Andor
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On 2020. Jul 17., at 2:51, Patrick Hunt <
>>>>>>>>>>>>>> phunt@apache.org> wrote:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> I updated the job I linked earlier based on what's
>>>>>>>>>>>>>> the latest on
>>>>>>>>>> the
>>>>>>>>>>>>> legacy
>>>>>>>>>>>>>> jenkins. It ran successfully
>>>>>>>>>>>>>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> I didn't replicate every config setting - main gap
>>>>>>>>>>>>>> is the spotbugs
>>>>>>>>>>>>>> post-build, which seems to be missing from the new
>>>>>>>>>>>>>> jenkins plugins.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> That's just maven master though. Not sure about the
>>>>>>>>>>>>>> rest. Can we do
>>>>>>>>>>>> more
>>>>>>>>>>>>> of
>>>>>>>>>>>>>> a "matrix" config in the new system vs cloning all
>>>>>>>>>>>>>> the time?
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Patrick
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt <
>>>>>>>>>>>>>> phunt@apache.org>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>> On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt <
>>>>>>>>>>>>>>> phunt@apache.org>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> On Thu, Jul 16, 2020 at 12:56 PM Enrico
>>>>>>>>>>>>>>>> Olivelli <
>>>>>>>>>>>> eolivelli@gmail.com>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> FYI
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Fun. I do notice it says "Hadoop and related
>>>>>>>>>>>>>>>> projects have their
>>>>>>>>>>> own
>>>>>>>>>>>>>>>> migration path to follow" - any insight on
>>>>>>>>>>>>>>>> that? We are or are
>>>>>>>>>> not
>>>>>>>>>>>>> lumped
>>>>>>>>>>>>>>>> in? I would assume we are?
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> This (eventual migration) came up a while back
>>>>>>>>>>>>>>>> on the Hadoop PMC
>>>>>>>>>>> and
>>>>>>>>>>>> I
>>>>>>>>>>>>>>>> volunteered to try for us (ZK). I was never
>>>>>>>>>>>>>>>> able to get it to
>>>>>>>>>>> work, I
>>>>>>>>>>>>>>>> provided feedback to infra  but they never got
>>>>>>>>>>>>>>>> back, as such we
>>>>>>>>>>> have
>>>>>>>>>>>> a
>>>>>>>>>>>>>>>> project here that's not working with some basic
>>>>>>>>>>>>>>>> dependencies
>>>>>>>>>>> missing:
>>>>>>>>>>>>>>>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> That said, we can try again. Can we verify
>>>>>>>>>>>>>>>> where ZK is supposed
>>>>>>>>>> to
>>>>>>>>>>>>> land?
>>>>>>>>>>>>>>>> Perhaps we can try to delete and recreate the
>>>>>>>>>>>>>>>> POC job I created
>>>>>>>>>> at
>>>>>>>>>>>> that
>>>>>>>>>>>>>>>> link to see if we can get it working?
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> I see another email thread on the list saying
>>>>>>>>>>>>>>> that we are part of
>>>>>>>>>>> said
>>>>>>>>>>>>>>> "related projects". We are expected to move to
>>>>>>>>>>>>>>> http://ci-hadoop.apache.org/ within 4 weeks.
>>>>>>>>>>>>>>> Seems nodes are
>>>>>>>>>>> already
>>>>>>>>>>>>>>> being removed/migrated from the "H#" pool.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Also this:
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> There are over 400 plugins on the current
>>>>>>>>>>>>>>> builds.apache.org -
>>>>>>>>>> most
>>>>>>>>>>> of
>>>>>>>>>>>>> which
>>>>>>>>>>>>>>> we don't need any more, or are replaced with
>>>>>>>>>>>>>>> different plugins on
>>>>>>>>>>> the
>>>>>>>>>>>>> new
>>>>>>>>>>>>>>> system. I expect there may be some plugins we
>>>>>>>>>>>>>>> still need to
>>>>>>>>>> install
>>>>>>>>>>> to
>>>>>>>>>>>>> get
>>>>>>>>>>>>>>> you going again, which is why it is vitally
>>>>>>>>>>>>>>> important that you
>>>>>>>>>> start
>>>>>>>>>>>>>>> testing and migrating your jobs over *now*. You
>>>>>>>>>>>>>>> should all have
>>>>>>>>>>> auth.
>>>>>>>>>>>>>>> Any questions, feel free to email the
>>>>>>>>>> hadoop-migrations@apache.org
>>>>>>>>>>>>> list if
>>>>>>>>>>>>>>> you are one of the projects listed below. The
>>>>>>>>>>>>>>> rest of you, not
>>>>>>>>>>>> listed, a
>>>>>>>>>>>>>>> similar email to this one will be posted for you
>>>>>>>>>>>>>>> shortly on
>>>>>>>>>>>> builds@a.o.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> full details
>>>>>>>>>>>>>>> 
>>>>>>>> 
>>> https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
>>>>>>>>>>>>>>> Patrick
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Patrick
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> ---------- Forwarded message ---------
>>>>>>>>>>>>>>>>> Da: Gavin McDonald <gm...@apache.org>
>>>>>>>>>>>>>>>>> Date: Gio 16 Lug 2020, 18:33
>>>>>>>>>>>>>>>>> Subject: [IMPORTANT] - Migration to ci-
>>>>>>>>>>>>>>>>> builds.a.o
>>>>>>>>>>>>>>>>> To: builds <bu...@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 Andor Molnar <an...@apache.org>.

Hi devs,

There’s some movement from Apache on Jenkins migration. Github account is now available on the new instance which will be useful for PreCommit builds. I started the tests.

Deadline (15 Aug) is approaching. Is there anything else which has fallen through the cracks and has to be migrated to the new instance?

Andor



> On 2020. Jul 24., at 19:15, Patrick Hunt <ph...@apache.org> wrote:
> 
> On Fri, Jul 24, 2020 at 3:05 AM Andor Molnar <an...@apache.org> wrote:
> 
>> Hi,
>> 
>> Jenkinsfile is now committed to master, 3.5 and 3.6 branches. Build is
>> running here:
>> 
>> https://ci-hadoop.apache.org/view/ZooKeeper/job/zookeeper-master-maven-multipipeline/
>> 
>> I use standard Git interface to access the repo, because using GitHub
>> means that branch discovery has to run through the github API. The problem
>> with this is that I haven’t specified credentials and anonymous access is
>> limited by some quota, meaning the discovery process takes ages (1-2 hours).
>> 
>> Builds are running fine except I see a lot of concurrent builds on master
>> without any meaningful SCM change. Odd. I will change pollSCM trigger to
>> run @hourly and will see how it goes.
>> 
>> What’s outstanding?
>> 
>> - JDKs: currently only two: 8, 11 (LTS versions). What other JDKs would
>> you like to run against?
>> 
>> - GitHub Pull Requests precommit job: I have no idea how to do this, but I
>> suspect we have to use the GitHub Api for this to work.
>> 
>> 
> Not sure if this is helpful but I saw it recently:
> 
>> we need ability to trigger builds on pull request creation/updates which
> 
>> requires the plug-in below or similar:
> 
>> https://plugins.jenkins.io/ghprb/
> 
> 
> 
> That plugin is deprecated and not recommended for use .
> 
> 
> I have installed the *branch source plugin instead*, hopefully that works
> for
> 
> you.
> 
> 
> If not, let's investigate further what else we can do
> 
> 
> 
>> - Windows build: there’s no Windows agent available currently in the new
>> instance.
>> 
>> - Ant builds: do we need this?
>> 
>> Please share your thoughts.
>> 
>> Regards,
>> Andor
>> 
>> 
>> 
>> 
>>> On 2020. Jul 23., at 22:08, Andor Molnar <an...@apache.org> wrote:
>>> 
>>> Hi folks,
>>> 
>>> PR is available: https://github.com/apache/zookeeper/pull/1409
>>> 
>>> Andor
>>> 
>>> 
>>> 
>>> On Thu, 2020-07-23 at 11:32 +0200, Andor Molnar wrote:
>>>> Created a Jira for the task:
>>>> 
>>>> https://issues.apache.org/jira/browse/ZOOKEEPER-3896
>>>> 
>>>> Andor
>>>> 
>>>> 
>>>> 
>>>>> On 2020. Jul 21., at 12:10, Andor Molnar <an...@apache.org> wrote:
>>>>> 
>>>>> Where’s that example…?
>>>>> 
>>>>> 
>>>>> 
>>>>>> On 2020. Jul 20., at 20:02, Enrico Olivelli <eo...@gmail.com>
>>>>>> wrote:
>>>>>> 
>>>>>> Il Lun 20 Lug 2020, 19:40 Andor Molnar <an...@apache.org> ha
>>>>>> scritto:
>>>>>> 
>>>>>>> Hi Enrico,
>>>>>>> 
>>>>>>> No worries, I only created a few jobs to make some progress,
>>>>>>> but feel free
>>>>>>> to ignore that and do it in a better way. The “View” or
>>>>>>> “Folder” that I was
>>>>>>> adding jobs is
>>>>>>> 
>>>>>>> https://ci-hadoop.apache.org/view/ZooKeeper/
>>>>>>> 
>>>>>>> 
>>>>>>> Andor
>>>>>>> 
>>>>>> 
>>>>>> This is an example from Apache Maven  project. It is very complex
>>>>>> because
>>>>>> tests are in another repo and for lots if other reasons. We just
>>>>>> have to
>>>>>> create a simpler file.
>>>>>> 
>>>>>> If nobody volunteers I can try to spend some time but I won't
>>>>>> have a fast
>>>>>> pace these weeks
>>>>>> 
>>>>>> 
>>>>>> Enrico
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>> 
>>>>>>>> On 2020. Jul 20., at 19:34, Enrico Olivelli <
>>>>>>>> eolivelli@gmail.com> wrote:
>>>>>>>> 
>>>>>>>> Il Lun 20 Lug 2020, 19:02 Patrick Hunt <ph...@apache.org> ha
>>>>>>>> scritto:
>>>>>>>> 
>>>>>>>>> On Mon, Jul 20, 2020 at 9:47 AM Enrico Olivelli <
>>>>>>>>> eolivelli@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>>> Il Lun 20 Lug 2020, 18:41 Patrick Hunt <ph...@apache.org>
>>>>>>>>>> ha scritto:
>>>>>>>>>> 
>>>>>>>>>>> On Sat, Jul 18, 2020 at 12:20 PM Andor Molnar <
>>>>>>>>>>> andor@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>>>> Hi Pat,
>>>>>>>>>>>> 
>>>>>>>>>>>> I have admin rights in the new system too and
>>>>>>>>>>>> probably can work on
>>>>>>>>> this
>>>>>>>>>>> on
>>>>>>>>>>>> Monday.
>>>>>>>>>>>> What’s “matrix” config? Shouldn’t we just replicate
>>>>>>>>>>>> the same jobs on
>>>>>>>>>> the
>>>>>>>>>>>> new instance?
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>> Not sure on the exact name/feature but "matrix" is
>>>>>>>>>>> basically the
>>>>>>>>> ability
>>>>>>>>>> to
>>>>>>>>>>> say "run this build/test across a set of JDK versions"
>>>>>>>>>>> rather than a
>>>>>>>>>> single
>>>>>>>>>>> version. As a result, instead of 3 jobs for zk3.6.0,
>>>>>>>>>>> jdk 1/2/3 you end
>>>>>>>>> up
>>>>>>>>>>> with a single job which runs three times, one for each
>>>>>>>>>>> jdk type and
>>>>>>>>>>> summarizes the results. I've seen this before, I assume
>>>>>>>>>>> it's a feature
>>>>>>>>> of
>>>>>>>>>>> jenkins itself?
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> We should use Jenkins files and this configuration will
>>>>>>>>>> be easy and
>>>>>>>>>> committed to git
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> The ability to do "gitops" would be amazing!
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> Yes.
>>>>>>>> But I saw on Slack that Andor already started to create new
>>>>>>>> jobs.
>>>>>>>> We should do only one way in order not to waste time.
>>>>>>>> 
>>>>>>>> Andor can you please share your work?
>>>>>>>> Thanks for doing it
>>>>>>>> 
>>>>>>>> Enrico
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>>> Patrick
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> Enrico
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>>> Patrick
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>>> Andor
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>>> On 2020. Jul 17., at 2:51, Patrick Hunt <
>>>>>>>>>>>>> phunt@apache.org> wrote:
>>>>>>>>>>>>> 
>>>>>>>>>>>>> I updated the job I linked earlier based on what's
>>>>>>>>>>>>> the latest on
>>>>>>>>> the
>>>>>>>>>>>> legacy
>>>>>>>>>>>>> jenkins. It ran successfully
>>>>>>>>>>>>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
>>>>>>>>>>>>> 
>>>>>>>>>>>>> I didn't replicate every config setting - main gap
>>>>>>>>>>>>> is the spotbugs
>>>>>>>>>>>>> post-build, which seems to be missing from the new
>>>>>>>>>>>>> jenkins plugins.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> That's just maven master though. Not sure about the
>>>>>>>>>>>>> rest. Can we do
>>>>>>>>>>> more
>>>>>>>>>>>> of
>>>>>>>>>>>>> a "matrix" config in the new system vs cloning all
>>>>>>>>>>>>> the time?
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Patrick
>>>>>>>>>>>>> 
>>>>>>>>>>>>> On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt <
>>>>>>>>>>>>> phunt@apache.org>
>>>>>>>>>> wrote:
>>>>>>>>>>>>>> On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt <
>>>>>>>>>>>>>> phunt@apache.org>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> On Thu, Jul 16, 2020 at 12:56 PM Enrico
>>>>>>>>>>>>>>> Olivelli <
>>>>>>>>>>> eolivelli@gmail.com>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> FYI
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Fun. I do notice it says "Hadoop and related
>>>>>>>>>>>>>>> projects have their
>>>>>>>>>> own
>>>>>>>>>>>>>>> migration path to follow" - any insight on
>>>>>>>>>>>>>>> that? We are or are
>>>>>>>>> not
>>>>>>>>>>>> lumped
>>>>>>>>>>>>>>> in? I would assume we are?
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> This (eventual migration) came up a while back
>>>>>>>>>>>>>>> on the Hadoop PMC
>>>>>>>>>> and
>>>>>>>>>>> I
>>>>>>>>>>>>>>> volunteered to try for us (ZK). I was never
>>>>>>>>>>>>>>> able to get it to
>>>>>>>>>> work, I
>>>>>>>>>>>>>>> provided feedback to infra  but they never got
>>>>>>>>>>>>>>> back, as such we
>>>>>>>>>> have
>>>>>>>>>>> a
>>>>>>>>>>>>>>> project here that's not working with some basic
>>>>>>>>>>>>>>> dependencies
>>>>>>>>>> missing:
>>>>>>>>>>>>>>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> That said, we can try again. Can we verify
>>>>>>>>>>>>>>> where ZK is supposed
>>>>>>>>> to
>>>>>>>>>>>> land?
>>>>>>>>>>>>>>> Perhaps we can try to delete and recreate the
>>>>>>>>>>>>>>> POC job I created
>>>>>>>>> at
>>>>>>>>>>> that
>>>>>>>>>>>>>>> link to see if we can get it working?
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> I see another email thread on the list saying
>>>>>>>>>>>>>> that we are part of
>>>>>>>>>> said
>>>>>>>>>>>>>> "related projects". We are expected to move to
>>>>>>>>>>>>>> http://ci-hadoop.apache.org/ within 4 weeks.
>>>>>>>>>>>>>> Seems nodes are
>>>>>>>>>> already
>>>>>>>>>>>>>> being removed/migrated from the "H#" pool.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Also this:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> There are over 400 plugins on the current
>>>>>>>>>>>>>> builds.apache.org -
>>>>>>>>> most
>>>>>>>>>> of
>>>>>>>>>>>> which
>>>>>>>>>>>>>> we don't need any more, or are replaced with
>>>>>>>>>>>>>> different plugins on
>>>>>>>>>> the
>>>>>>>>>>>> new
>>>>>>>>>>>>>> system. I expect there may be some plugins we
>>>>>>>>>>>>>> still need to
>>>>>>>>> install
>>>>>>>>>> to
>>>>>>>>>>>> get
>>>>>>>>>>>>>> you going again, which is why it is vitally
>>>>>>>>>>>>>> important that you
>>>>>>>>> start
>>>>>>>>>>>>>> testing and migrating your jobs over *now*. You
>>>>>>>>>>>>>> should all have
>>>>>>>>>> auth.
>>>>>>>>>>>>>> Any questions, feel free to email the
>>>>>>>>> hadoop-migrations@apache.org
>>>>>>>>>>>> list if
>>>>>>>>>>>>>> you are one of the projects listed below. The
>>>>>>>>>>>>>> rest of you, not
>>>>>>>>>>> listed, a
>>>>>>>>>>>>>> similar email to this one will be posted for you
>>>>>>>>>>>>>> shortly on
>>>>>>>>>>> builds@a.o.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> full details
>>>>>>>>>>>>>> 
>>>>>>> 
>> https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
>>>>>>>>>>>>>> Patrick
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Patrick
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> ---------- Forwarded message ---------
>>>>>>>>>>>>>>>> Da: Gavin McDonald <gm...@apache.org>
>>>>>>>>>>>>>>>> Date: Gio 16 Lug 2020, 18:33
>>>>>>>>>>>>>>>> Subject: [IMPORTANT] - Migration to ci-
>>>>>>>>>>>>>>>> builds.a.o
>>>>>>>>>>>>>>>> To: builds <bu...@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 Patrick Hunt <ph...@apache.org>.

On Fri, Jul 24, 2020 at 3:05 AM Andor Molnar <an...@apache.org> wrote:

> Hi,
>
> Jenkinsfile is now committed to master, 3.5 and 3.6 branches. Build is
> running here:
>
> https://ci-hadoop.apache.org/view/ZooKeeper/job/zookeeper-master-maven-multipipeline/
>
> I use standard Git interface to access the repo, because using GitHub
> means that branch discovery has to run through the github API. The problem
> with this is that I haven’t specified credentials and anonymous access is
> limited by some quota, meaning the discovery process takes ages (1-2 hours).
>
> Builds are running fine except I see a lot of concurrent builds on master
> without any meaningful SCM change. Odd. I will change pollSCM trigger to
> run @hourly and will see how it goes.
>
> What’s outstanding?
>
> - JDKs: currently only two: 8, 11 (LTS versions). What other JDKs would
> you like to run against?
>
> - GitHub Pull Requests precommit job: I have no idea how to do this, but I
> suspect we have to use the GitHub Api for this to work.
>
>
Not sure if this is helpful but I saw it recently:

> we need ability to trigger builds on pull request creation/updates which

> requires the plug-in below or similar:

> https://plugins.jenkins.io/ghprb/



That plugin is deprecated and not recommended for use .


I have installed the *branch source plugin instead*, hopefully that works
for

you.


If not, let's investigate further what else we can do



> - Windows build: there’s no Windows agent available currently in the new
> instance.
>
> - Ant builds: do we need this?
>
> Please share your thoughts.
>
> Regards,
> Andor
>
>
>
>
> > On 2020. Jul 23., at 22:08, Andor Molnar <an...@apache.org> wrote:
> >
> > Hi folks,
> >
> > PR is available: https://github.com/apache/zookeeper/pull/1409
> >
> > Andor
> >
> >
> >
> > On Thu, 2020-07-23 at 11:32 +0200, Andor Molnar wrote:
> >> Created a Jira for the task:
> >>
> >> https://issues.apache.org/jira/browse/ZOOKEEPER-3896
> >>
> >> Andor
> >>
> >>
> >>
> >>> On 2020. Jul 21., at 12:10, Andor Molnar <an...@apache.org> wrote:
> >>>
> >>> Where’s that example…?
> >>>
> >>>
> >>>
> >>>> On 2020. Jul 20., at 20:02, Enrico Olivelli <eo...@gmail.com>
> >>>> wrote:
> >>>>
> >>>> Il Lun 20 Lug 2020, 19:40 Andor Molnar <an...@apache.org> ha
> >>>> scritto:
> >>>>
> >>>>> Hi Enrico,
> >>>>>
> >>>>> No worries, I only created a few jobs to make some progress,
> >>>>> but feel free
> >>>>> to ignore that and do it in a better way. The “View” or
> >>>>> “Folder” that I was
> >>>>> adding jobs is
> >>>>>
> >>>>> https://ci-hadoop.apache.org/view/ZooKeeper/
> >>>>>
> >>>>>
> >>>>> Andor
> >>>>>
> >>>>
> >>>> This is an example from Apache Maven  project. It is very complex
> >>>> because
> >>>> tests are in another repo and for lots if other reasons. We just
> >>>> have to
> >>>> create a simpler file.
> >>>>
> >>>> If nobody volunteers I can try to spend some time but I won't
> >>>> have a fast
> >>>> pace these weeks
> >>>>
> >>>>
> >>>> Enrico
> >>>>
> >>>>
> >>>>
> >>>>>
> >>>>>> On 2020. Jul 20., at 19:34, Enrico Olivelli <
> >>>>>> eolivelli@gmail.com> wrote:
> >>>>>>
> >>>>>> Il Lun 20 Lug 2020, 19:02 Patrick Hunt <ph...@apache.org> ha
> >>>>>> scritto:
> >>>>>>
> >>>>>>> On Mon, Jul 20, 2020 at 9:47 AM Enrico Olivelli <
> >>>>>>> eolivelli@gmail.com>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> Il Lun 20 Lug 2020, 18:41 Patrick Hunt <ph...@apache.org>
> >>>>>>>> ha scritto:
> >>>>>>>>
> >>>>>>>>> On Sat, Jul 18, 2020 at 12:20 PM Andor Molnar <
> >>>>>>>>> andor@apache.org>
> >>>>>>> wrote:
> >>>>>>>>>> Hi Pat,
> >>>>>>>>>>
> >>>>>>>>>> I have admin rights in the new system too and
> >>>>>>>>>> probably can work on
> >>>>>>> this
> >>>>>>>>> on
> >>>>>>>>>> Monday.
> >>>>>>>>>> What’s “matrix” config? Shouldn’t we just replicate
> >>>>>>>>>> the same jobs on
> >>>>>>>> the
> >>>>>>>>>> new instance?
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>> Not sure on the exact name/feature but "matrix" is
> >>>>>>>>> basically the
> >>>>>>> ability
> >>>>>>>> to
> >>>>>>>>> say "run this build/test across a set of JDK versions"
> >>>>>>>>> rather than a
> >>>>>>>> single
> >>>>>>>>> version. As a result, instead of 3 jobs for zk3.6.0,
> >>>>>>>>> jdk 1/2/3 you end
> >>>>>>> up
> >>>>>>>>> with a single job which runs three times, one for each
> >>>>>>>>> jdk type and
> >>>>>>>>> summarizes the results. I've seen this before, I assume
> >>>>>>>>> it's a feature
> >>>>>>> of
> >>>>>>>>> jenkins itself?
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> We should use Jenkins files and this configuration will
> >>>>>>>> be easy and
> >>>>>>>> committed to git
> >>>>>>>>
> >>>>>>>
> >>>>>>> The ability to do "gitops" would be amazing!
> >>>>>>>
> >>>>>>
> >>>>>> Yes.
> >>>>>> But I saw on Slack that Andor already started to create new
> >>>>>> jobs.
> >>>>>> We should do only one way in order not to waste time.
> >>>>>>
> >>>>>> Andor can you please share your work?
> >>>>>> Thanks for doing it
> >>>>>>
> >>>>>> Enrico
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> Patrick
> >>>>>>>
> >>>>>>>
> >>>>>>>> Enrico
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> Patrick
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>> Andor
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>> On 2020. Jul 17., at 2:51, Patrick Hunt <
> >>>>>>>>>>> phunt@apache.org> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> I updated the job I linked earlier based on what's
> >>>>>>>>>>> the latest on
> >>>>>>> the
> >>>>>>>>>> legacy
> >>>>>>>>>>> jenkins. It ran successfully
> >>>>>>>>>>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
> >>>>>>>>>>>
> >>>>>>>>>>> I didn't replicate every config setting - main gap
> >>>>>>>>>>> is the spotbugs
> >>>>>>>>>>> post-build, which seems to be missing from the new
> >>>>>>>>>>> jenkins plugins.
> >>>>>>>>>>>
> >>>>>>>>>>> That's just maven master though. Not sure about the
> >>>>>>>>>>> rest. Can we do
> >>>>>>>>> more
> >>>>>>>>>> of
> >>>>>>>>>>> a "matrix" config in the new system vs cloning all
> >>>>>>>>>>> the time?
> >>>>>>>>>>>
> >>>>>>>>>>> Patrick
> >>>>>>>>>>>
> >>>>>>>>>>> On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt <
> >>>>>>>>>>> phunt@apache.org>
> >>>>>>>> wrote:
> >>>>>>>>>>>> On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt <
> >>>>>>>>>>>> phunt@apache.org>
> >>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Thu, Jul 16, 2020 at 12:56 PM Enrico
> >>>>>>>>>>>>> Olivelli <
> >>>>>>>>> eolivelli@gmail.com>
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> FYI
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Fun. I do notice it says "Hadoop and related
> >>>>>>>>>>>>> projects have their
> >>>>>>>> own
> >>>>>>>>>>>>> migration path to follow" - any insight on
> >>>>>>>>>>>>> that? We are or are
> >>>>>>> not
> >>>>>>>>>> lumped
> >>>>>>>>>>>>> in? I would assume we are?
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> This (eventual migration) came up a while back
> >>>>>>>>>>>>> on the Hadoop PMC
> >>>>>>>> and
> >>>>>>>>> I
> >>>>>>>>>>>>> volunteered to try for us (ZK). I was never
> >>>>>>>>>>>>> able to get it to
> >>>>>>>> work, I
> >>>>>>>>>>>>> provided feedback to infra  but they never got
> >>>>>>>>>>>>> back, as such we
> >>>>>>>> have
> >>>>>>>>> a
> >>>>>>>>>>>>> project here that's not working with some basic
> >>>>>>>>>>>>> dependencies
> >>>>>>>> missing:
> >>>>>>>>>>>>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> That said, we can try again. Can we verify
> >>>>>>>>>>>>> where ZK is supposed
> >>>>>>> to
> >>>>>>>>>> land?
> >>>>>>>>>>>>> Perhaps we can try to delete and recreate the
> >>>>>>>>>>>>> POC job I created
> >>>>>>> at
> >>>>>>>>> that
> >>>>>>>>>>>>> link to see if we can get it working?
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>> I see another email thread on the list saying
> >>>>>>>>>>>> that we are part of
> >>>>>>>> said
> >>>>>>>>>>>> "related projects". We are expected to move to
> >>>>>>>>>>>> http://ci-hadoop.apache.org/ within 4 weeks.
> >>>>>>>>>>>> Seems nodes are
> >>>>>>>> already
> >>>>>>>>>>>> being removed/migrated from the "H#" pool.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Also this:
> >>>>>>>>>>>>
> >>>>>>>>>>>> There are over 400 plugins on the current
> >>>>>>>>>>>> builds.apache.org -
> >>>>>>> most
> >>>>>>>> of
> >>>>>>>>>> which
> >>>>>>>>>>>> we don't need any more, or are replaced with
> >>>>>>>>>>>> different plugins on
> >>>>>>>> the
> >>>>>>>>>> new
> >>>>>>>>>>>> system. I expect there may be some plugins we
> >>>>>>>>>>>> still need to
> >>>>>>> install
> >>>>>>>> to
> >>>>>>>>>> get
> >>>>>>>>>>>> you going again, which is why it is vitally
> >>>>>>>>>>>> important that you
> >>>>>>> start
> >>>>>>>>>>>> testing and migrating your jobs over *now*. You
> >>>>>>>>>>>> should all have
> >>>>>>>> auth.
> >>>>>>>>>>>> Any questions, feel free to email the
> >>>>>>> hadoop-migrations@apache.org
> >>>>>>>>>> list if
> >>>>>>>>>>>> you are one of the projects listed below. The
> >>>>>>>>>>>> rest of you, not
> >>>>>>>>> listed, a
> >>>>>>>>>>>> similar email to this one will be posted for you
> >>>>>>>>>>>> shortly on
> >>>>>>>>> builds@a.o.
> >>>>>>>>>>>>
> >>>>>>>>>>>> full details
> >>>>>>>>>>>>
> >>>>>
> https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
> >>>>>>>>>>>> Patrick
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>> Patrick
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> ---------- Forwarded message ---------
> >>>>>>>>>>>>>> Da: Gavin McDonald <gm...@apache.org>
> >>>>>>>>>>>>>> Date: Gio 16 Lug 2020, 18:33
> >>>>>>>>>>>>>> Subject: [IMPORTANT] - Migration to ci-
> >>>>>>>>>>>>>> builds.a.o
> >>>>>>>>>>>>>> To: builds <bu...@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 Andor Molnar <an...@apache.org>.

Hi,

Jenkinsfile is now committed to master, 3.5 and 3.6 branches. Build is running here:
https://ci-hadoop.apache.org/view/ZooKeeper/job/zookeeper-master-maven-multipipeline/

I use standard Git interface to access the repo, because using GitHub means that branch discovery has to run through the github API. The problem with this is that I haven’t specified credentials and anonymous access is limited by some quota, meaning the discovery process takes ages (1-2 hours).

Builds are running fine except I see a lot of concurrent builds on master without any meaningful SCM change. Odd. I will change pollSCM trigger to run @hourly and will see how it goes.

What’s outstanding?

- JDKs: currently only two: 8, 11 (LTS versions). What other JDKs would you like to run against?

- GitHub Pull Requests precommit job: I have no idea how to do this, but I suspect we have to use the GitHub Api for this to work.

- Windows build: there’s no Windows agent available currently in the new instance.

- Ant builds: do we need this?

Please share your thoughts.

Regards,
Andor




> On 2020. Jul 23., at 22:08, Andor Molnar <an...@apache.org> wrote:
> 
> Hi folks,
> 
> PR is available: https://github.com/apache/zookeeper/pull/1409
> 
> Andor
> 
> 
> 
> On Thu, 2020-07-23 at 11:32 +0200, Andor Molnar wrote:
>> Created a Jira for the task:
>> 
>> https://issues.apache.org/jira/browse/ZOOKEEPER-3896
>> 
>> Andor
>> 
>> 
>> 
>>> On 2020. Jul 21., at 12:10, Andor Molnar <an...@apache.org> wrote:
>>> 
>>> Where’s that example…?
>>> 
>>> 
>>> 
>>>> On 2020. Jul 20., at 20:02, Enrico Olivelli <eo...@gmail.com>
>>>> wrote:
>>>> 
>>>> Il Lun 20 Lug 2020, 19:40 Andor Molnar <an...@apache.org> ha
>>>> scritto:
>>>> 
>>>>> Hi Enrico,
>>>>> 
>>>>> No worries, I only created a few jobs to make some progress,
>>>>> but feel free
>>>>> to ignore that and do it in a better way. The “View” or
>>>>> “Folder” that I was
>>>>> adding jobs is
>>>>> 
>>>>> https://ci-hadoop.apache.org/view/ZooKeeper/
>>>>> 
>>>>> 
>>>>> Andor
>>>>> 
>>>> 
>>>> This is an example from Apache Maven  project. It is very complex
>>>> because
>>>> tests are in another repo and for lots if other reasons. We just
>>>> have to
>>>> create a simpler file.
>>>> 
>>>> If nobody volunteers I can try to spend some time but I won't
>>>> have a fast
>>>> pace these weeks
>>>> 
>>>> 
>>>> Enrico
>>>> 
>>>> 
>>>> 
>>>>> 
>>>>>> On 2020. Jul 20., at 19:34, Enrico Olivelli <
>>>>>> eolivelli@gmail.com> wrote:
>>>>>> 
>>>>>> Il Lun 20 Lug 2020, 19:02 Patrick Hunt <ph...@apache.org> ha
>>>>>> scritto:
>>>>>> 
>>>>>>> On Mon, Jul 20, 2020 at 9:47 AM Enrico Olivelli <
>>>>>>> eolivelli@gmail.com>
>>>>>>> wrote:
>>>>>>> 
>>>>>>>> Il Lun 20 Lug 2020, 18:41 Patrick Hunt <ph...@apache.org>
>>>>>>>> ha scritto:
>>>>>>>> 
>>>>>>>>> On Sat, Jul 18, 2020 at 12:20 PM Andor Molnar <
>>>>>>>>> andor@apache.org>
>>>>>>> wrote:
>>>>>>>>>> Hi Pat,
>>>>>>>>>> 
>>>>>>>>>> I have admin rights in the new system too and
>>>>>>>>>> probably can work on
>>>>>>> this
>>>>>>>>> on
>>>>>>>>>> Monday.
>>>>>>>>>> What’s “matrix” config? Shouldn’t we just replicate
>>>>>>>>>> the same jobs on
>>>>>>>> the
>>>>>>>>>> new instance?
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> Not sure on the exact name/feature but "matrix" is
>>>>>>>>> basically the
>>>>>>> ability
>>>>>>>> to
>>>>>>>>> say "run this build/test across a set of JDK versions"
>>>>>>>>> rather than a
>>>>>>>> single
>>>>>>>>> version. As a result, instead of 3 jobs for zk3.6.0,
>>>>>>>>> jdk 1/2/3 you end
>>>>>>> up
>>>>>>>>> with a single job which runs three times, one for each
>>>>>>>>> jdk type and
>>>>>>>>> summarizes the results. I've seen this before, I assume
>>>>>>>>> it's a feature
>>>>>>> of
>>>>>>>>> jenkins itself?
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> We should use Jenkins files and this configuration will
>>>>>>>> be easy and
>>>>>>>> committed to git
>>>>>>>> 
>>>>>>> 
>>>>>>> The ability to do "gitops" would be amazing!
>>>>>>> 
>>>>>> 
>>>>>> Yes.
>>>>>> But I saw on Slack that Andor already started to create new
>>>>>> jobs.
>>>>>> We should do only one way in order not to waste time.
>>>>>> 
>>>>>> Andor can you please share your work?
>>>>>> Thanks for doing it
>>>>>> 
>>>>>> Enrico
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>> Patrick
>>>>>>> 
>>>>>>> 
>>>>>>>> Enrico
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>>> Patrick
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> Andor
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>>> On 2020. Jul 17., at 2:51, Patrick Hunt <
>>>>>>>>>>> phunt@apache.org> wrote:
>>>>>>>>>>> 
>>>>>>>>>>> I updated the job I linked earlier based on what's
>>>>>>>>>>> the latest on
>>>>>>> the
>>>>>>>>>> legacy
>>>>>>>>>>> jenkins. It ran successfully
>>>>>>>>>>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
>>>>>>>>>>> 
>>>>>>>>>>> I didn't replicate every config setting - main gap
>>>>>>>>>>> is the spotbugs
>>>>>>>>>>> post-build, which seems to be missing from the new
>>>>>>>>>>> jenkins plugins.
>>>>>>>>>>> 
>>>>>>>>>>> That's just maven master though. Not sure about the
>>>>>>>>>>> rest. Can we do
>>>>>>>>> more
>>>>>>>>>> of
>>>>>>>>>>> a "matrix" config in the new system vs cloning all
>>>>>>>>>>> the time?
>>>>>>>>>>> 
>>>>>>>>>>> Patrick
>>>>>>>>>>> 
>>>>>>>>>>> On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt <
>>>>>>>>>>> phunt@apache.org>
>>>>>>>> wrote:
>>>>>>>>>>>> On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt <
>>>>>>>>>>>> phunt@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>>>>> 
>>>>>>>>>>>>> On Thu, Jul 16, 2020 at 12:56 PM Enrico
>>>>>>>>>>>>> Olivelli <
>>>>>>>>> eolivelli@gmail.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> FYI
>>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Fun. I do notice it says "Hadoop and related
>>>>>>>>>>>>> projects have their
>>>>>>>> own
>>>>>>>>>>>>> migration path to follow" - any insight on
>>>>>>>>>>>>> that? We are or are
>>>>>>> not
>>>>>>>>>> lumped
>>>>>>>>>>>>> in? I would assume we are?
>>>>>>>>>>>>> 
>>>>>>>>>>>>> This (eventual migration) came up a while back
>>>>>>>>>>>>> on the Hadoop PMC
>>>>>>>> and
>>>>>>>>> I
>>>>>>>>>>>>> volunteered to try for us (ZK). I was never
>>>>>>>>>>>>> able to get it to
>>>>>>>> work, I
>>>>>>>>>>>>> provided feedback to infra  but they never got
>>>>>>>>>>>>> back, as such we
>>>>>>>> have
>>>>>>>>> a
>>>>>>>>>>>>> project here that's not working with some basic
>>>>>>>>>>>>> dependencies
>>>>>>>> missing:
>>>>>>>>>>>>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/
>>>>>>>>>>>>> 
>>>>>>>>>>>>> That said, we can try again. Can we verify
>>>>>>>>>>>>> where ZK is supposed
>>>>>>> to
>>>>>>>>>> land?
>>>>>>>>>>>>> Perhaps we can try to delete and recreate the
>>>>>>>>>>>>> POC job I created
>>>>>>> at
>>>>>>>>> that
>>>>>>>>>>>>> link to see if we can get it working?
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>> I see another email thread on the list saying
>>>>>>>>>>>> that we are part of
>>>>>>>> said
>>>>>>>>>>>> "related projects". We are expected to move to
>>>>>>>>>>>> http://ci-hadoop.apache.org/ within 4 weeks.
>>>>>>>>>>>> Seems nodes are
>>>>>>>> already
>>>>>>>>>>>> being removed/migrated from the "H#" pool.
>>>>>>>>>>>> 
>>>>>>>>>>>> Also this:
>>>>>>>>>>>> 
>>>>>>>>>>>> There are over 400 plugins on the current
>>>>>>>>>>>> builds.apache.org -
>>>>>>> most
>>>>>>>> of
>>>>>>>>>> which
>>>>>>>>>>>> we don't need any more, or are replaced with
>>>>>>>>>>>> different plugins on
>>>>>>>> the
>>>>>>>>>> new
>>>>>>>>>>>> system. I expect there may be some plugins we
>>>>>>>>>>>> still need to
>>>>>>> install
>>>>>>>> to
>>>>>>>>>> get
>>>>>>>>>>>> you going again, which is why it is vitally
>>>>>>>>>>>> important that you
>>>>>>> start
>>>>>>>>>>>> testing and migrating your jobs over *now*. You
>>>>>>>>>>>> should all have
>>>>>>>> auth.
>>>>>>>>>>>> Any questions, feel free to email the
>>>>>>> hadoop-migrations@apache.org
>>>>>>>>>> list if
>>>>>>>>>>>> you are one of the projects listed below. The
>>>>>>>>>>>> rest of you, not
>>>>>>>>> listed, a
>>>>>>>>>>>> similar email to this one will be posted for you
>>>>>>>>>>>> shortly on
>>>>>>>>> builds@a.o.
>>>>>>>>>>>> 
>>>>>>>>>>>> full details
>>>>>>>>>>>> 
>>>>> https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
>>>>>>>>>>>> Patrick
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>>> Patrick
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> ---------- Forwarded message ---------
>>>>>>>>>>>>>> Da: Gavin McDonald <gm...@apache.org>
>>>>>>>>>>>>>> Date: Gio 16 Lug 2020, 18:33
>>>>>>>>>>>>>> Subject: [IMPORTANT] - Migration to ci-
>>>>>>>>>>>>>> builds.a.o
>>>>>>>>>>>>>> To: builds <bu...@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 Andor Molnar <an...@apache.org>.

Hi folks,

PR is available: https://github.com/apache/zookeeper/pull/1409

Andor



On Thu, 2020-07-23 at 11:32 +0200, Andor Molnar wrote:
> Created a Jira for the task:
> 
> https://issues.apache.org/jira/browse/ZOOKEEPER-3896
> 
> Andor
> 
> 
> 
> > On 2020. Jul 21., at 12:10, Andor Molnar <an...@apache.org> wrote:
> > 
> > Where’s that example…?
> > 
> > 
> > 
> > > On 2020. Jul 20., at 20:02, Enrico Olivelli <eo...@gmail.com>
> > > wrote:
> > > 
> > > Il Lun 20 Lug 2020, 19:40 Andor Molnar <an...@apache.org> ha
> > > scritto:
> > > 
> > > > Hi Enrico,
> > > > 
> > > > No worries, I only created a few jobs to make some progress,
> > > > but feel free
> > > > to ignore that and do it in a better way. The “View” or
> > > > “Folder” that I was
> > > > adding jobs is
> > > > 
> > > > https://ci-hadoop.apache.org/view/ZooKeeper/
> > > > 
> > > > 
> > > > Andor
> > > > 
> > > 
> > > This is an example from Apache Maven  project. It is very complex
> > > because
> > > tests are in another repo and for lots if other reasons. We just
> > > have to
> > > create a simpler file.
> > > 
> > > If nobody volunteers I can try to spend some time but I won't
> > > have a fast
> > > pace these weeks
> > > 
> > > 
> > > Enrico
> > > 
> > > 
> > > 
> > > > 
> > > > > On 2020. Jul 20., at 19:34, Enrico Olivelli <
> > > > > eolivelli@gmail.com> wrote:
> > > > > 
> > > > > Il Lun 20 Lug 2020, 19:02 Patrick Hunt <ph...@apache.org> ha
> > > > > scritto:
> > > > > 
> > > > > > On Mon, Jul 20, 2020 at 9:47 AM Enrico Olivelli <
> > > > > > eolivelli@gmail.com>
> > > > > > wrote:
> > > > > > 
> > > > > > > Il Lun 20 Lug 2020, 18:41 Patrick Hunt <ph...@apache.org>
> > > > > > > ha scritto:
> > > > > > > 
> > > > > > > > On Sat, Jul 18, 2020 at 12:20 PM Andor Molnar <
> > > > > > > > andor@apache.org>
> > > > > > wrote:
> > > > > > > > > Hi Pat,
> > > > > > > > > 
> > > > > > > > > I have admin rights in the new system too and
> > > > > > > > > probably can work on
> > > > > > this
> > > > > > > > on
> > > > > > > > > Monday.
> > > > > > > > > What’s “matrix” config? Shouldn’t we just replicate
> > > > > > > > > the same jobs on
> > > > > > > the
> > > > > > > > > new instance?
> > > > > > > > > 
> > > > > > > > > 
> > > > > > > > Not sure on the exact name/feature but "matrix" is
> > > > > > > > basically the
> > > > > > ability
> > > > > > > to
> > > > > > > > say "run this build/test across a set of JDK versions"
> > > > > > > > rather than a
> > > > > > > single
> > > > > > > > version. As a result, instead of 3 jobs for zk3.6.0,
> > > > > > > > jdk 1/2/3 you end
> > > > > > up
> > > > > > > > with a single job which runs three times, one for each
> > > > > > > > jdk type and
> > > > > > > > summarizes the results. I've seen this before, I assume
> > > > > > > > it's a feature
> > > > > > of
> > > > > > > > jenkins itself?
> > > > > > > > 
> > > > > > > 
> > > > > > > We should use Jenkins files and this configuration will
> > > > > > > be easy and
> > > > > > > committed to git
> > > > > > > 
> > > > > > 
> > > > > > The ability to do "gitops" would be amazing!
> > > > > > 
> > > > > 
> > > > > Yes.
> > > > > But I saw on Slack that Andor already started to create new
> > > > > jobs.
> > > > > We should do only one way in order not to waste time.
> > > > > 
> > > > > Andor can you please share your work?
> > > > > Thanks for doing it
> > > > > 
> > > > > Enrico
> > > > > 
> > > > > 
> > > > > 
> > > > > > Patrick
> > > > > > 
> > > > > > 
> > > > > > > Enrico
> > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > > > Patrick
> > > > > > > > 
> > > > > > > > 
> > > > > > > > > Andor
> > > > > > > > > 
> > > > > > > > > 
> > > > > > > > > 
> > > > > > > > > > On 2020. Jul 17., at 2:51, Patrick Hunt <
> > > > > > > > > > phunt@apache.org> wrote:
> > > > > > > > > > 
> > > > > > > > > > I updated the job I linked earlier based on what's
> > > > > > > > > > the latest on
> > > > > > the
> > > > > > > > > legacy
> > > > > > > > > > jenkins. It ran successfully
> > > > > > > > > > https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
> > > > > > > > > > 
> > > > > > > > > > I didn't replicate every config setting - main gap
> > > > > > > > > > is the spotbugs
> > > > > > > > > > post-build, which seems to be missing from the new
> > > > > > > > > > jenkins plugins.
> > > > > > > > > > 
> > > > > > > > > > That's just maven master though. Not sure about the
> > > > > > > > > > rest. Can we do
> > > > > > > > more
> > > > > > > > > of
> > > > > > > > > > a "matrix" config in the new system vs cloning all
> > > > > > > > > > the time?
> > > > > > > > > > 
> > > > > > > > > > Patrick
> > > > > > > > > > 
> > > > > > > > > > On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt <
> > > > > > > > > > phunt@apache.org>
> > > > > > > wrote:
> > > > > > > > > > > On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt <
> > > > > > > > > > > phunt@apache.org>
> > > > > > > > wrote:
> > > > > > > > > > > > 
> > > > > > > > > > > > On Thu, Jul 16, 2020 at 12:56 PM Enrico
> > > > > > > > > > > > Olivelli <
> > > > > > > > eolivelli@gmail.com>
> > > > > > > > > > > > wrote:
> > > > > > > > > > > > 
> > > > > > > > > > > > > FYI
> > > > > > > > > > > > > 
> > > > > > > > > > > > 
> > > > > > > > > > > > Fun. I do notice it says "Hadoop and related
> > > > > > > > > > > > projects have their
> > > > > > > own
> > > > > > > > > > > > migration path to follow" - any insight on
> > > > > > > > > > > > that? We are or are
> > > > > > not
> > > > > > > > > lumped
> > > > > > > > > > > > in? I would assume we are?
> > > > > > > > > > > > 
> > > > > > > > > > > > This (eventual migration) came up a while back
> > > > > > > > > > > > on the Hadoop PMC
> > > > > > > and
> > > > > > > > I
> > > > > > > > > > > > volunteered to try for us (ZK). I was never
> > > > > > > > > > > > able to get it to
> > > > > > > work, I
> > > > > > > > > > > > provided feedback to infra  but they never got
> > > > > > > > > > > > back, as such we
> > > > > > > have
> > > > > > > > a
> > > > > > > > > > > > project here that's not working with some basic
> > > > > > > > > > > > dependencies
> > > > > > > missing:
> > > > > > > > > > > > https://ci-hadoop.apache.org/job/zookeeper-master-maven/
> > > > > > > > > > > > 
> > > > > > > > > > > > That said, we can try again. Can we verify
> > > > > > > > > > > > where ZK is supposed
> > > > > > to
> > > > > > > > > land?
> > > > > > > > > > > > Perhaps we can try to delete and recreate the
> > > > > > > > > > > > POC job I created
> > > > > > at
> > > > > > > > that
> > > > > > > > > > > > link to see if we can get it working?
> > > > > > > > > > > > 
> > > > > > > > > > > > 
> > > > > > > > > > > I see another email thread on the list saying
> > > > > > > > > > > that we are part of
> > > > > > > said
> > > > > > > > > > > "related projects". We are expected to move to
> > > > > > > > > > > http://ci-hadoop.apache.org/ within 4 weeks.
> > > > > > > > > > > Seems nodes are
> > > > > > > already
> > > > > > > > > > > being removed/migrated from the "H#" pool.
> > > > > > > > > > > 
> > > > > > > > > > > Also this:
> > > > > > > > > > > 
> > > > > > > > > > > There are over 400 plugins on the current
> > > > > > > > > > > builds.apache.org -
> > > > > > most
> > > > > > > of
> > > > > > > > > which
> > > > > > > > > > > we don't need any more, or are replaced with
> > > > > > > > > > > different plugins on
> > > > > > > the
> > > > > > > > > new
> > > > > > > > > > > system. I expect there may be some plugins we
> > > > > > > > > > > still need to
> > > > > > install
> > > > > > > to
> > > > > > > > > get
> > > > > > > > > > > you going again, which is why it is vitally
> > > > > > > > > > > important that you
> > > > > > start
> > > > > > > > > > > testing and migrating your jobs over *now*. You
> > > > > > > > > > > should all have
> > > > > > > auth.
> > > > > > > > > > > Any questions, feel free to email the
> > > > > > hadoop-migrations@apache.org
> > > > > > > > > list if
> > > > > > > > > > > you are one of the projects listed below. The
> > > > > > > > > > > rest of you, not
> > > > > > > > listed, a
> > > > > > > > > > > similar email to this one will be posted for you
> > > > > > > > > > > shortly on
> > > > > > > > builds@a.o.
> > > > > > > > > > > 
> > > > > > > > > > > full details
> > > > > > > > > > > 
> > > > https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
> > > > > > > > > > > Patrick
> > > > > > > > > > > 
> > > > > > > > > > > 
> > > > > > > > > > > 
> > > > > > > > > > > > Patrick
> > > > > > > > > > > > 
> > > > > > > > > > > > 
> > > > > > > > > > > > > ---------- Forwarded message ---------
> > > > > > > > > > > > > Da: Gavin McDonald <gm...@apache.org>
> > > > > > > > > > > > > Date: Gio 16 Lug 2020, 18:33
> > > > > > > > > > > > > Subject: [IMPORTANT] - Migration to ci-
> > > > > > > > > > > > > builds.a.o
> > > > > > > > > > > > > To: builds <bu...@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 Andor Molnar <an...@apache.org>.

Created a Jira for the task:

https://issues.apache.org/jira/browse/ZOOKEEPER-3896

Andor



> On 2020. Jul 21., at 12:10, Andor Molnar <an...@apache.org> wrote:
> 
> Where’s that example…?
> 
> 
> 
>> On 2020. Jul 20., at 20:02, Enrico Olivelli <eo...@gmail.com> wrote:
>> 
>> Il Lun 20 Lug 2020, 19:40 Andor Molnar <an...@apache.org> ha scritto:
>> 
>>> Hi Enrico,
>>> 
>>> No worries, I only created a few jobs to make some progress, but feel free
>>> to ignore that and do it in a better way. The “View” or “Folder” that I was
>>> adding jobs is
>>> 
>>> https://ci-hadoop.apache.org/view/ZooKeeper/
>>> 
>>> 
>>> Andor
>>> 
>> 
>> This is an example from Apache Maven  project. It is very complex because
>> tests are in another repo and for lots if other reasons. We just have to
>> create a simpler file.
>> 
>> If nobody volunteers I can try to spend some time but I won't have a fast
>> pace these weeks
>> 
>> 
>> Enrico
>> 
>> 
>> 
>>> 
>>> 
>>>> On 2020. Jul 20., at 19:34, Enrico Olivelli <eo...@gmail.com> wrote:
>>>> 
>>>> Il Lun 20 Lug 2020, 19:02 Patrick Hunt <ph...@apache.org> ha scritto:
>>>> 
>>>>> On Mon, Jul 20, 2020 at 9:47 AM Enrico Olivelli <eo...@gmail.com>
>>>>> wrote:
>>>>> 
>>>>>> Il Lun 20 Lug 2020, 18:41 Patrick Hunt <ph...@apache.org> ha scritto:
>>>>>> 
>>>>>>> On Sat, Jul 18, 2020 at 12:20 PM Andor Molnar <an...@apache.org>
>>>>> wrote:
>>>>>>> 
>>>>>>>> Hi Pat,
>>>>>>>> 
>>>>>>>> I have admin rights in the new system too and probably can work on
>>>>> this
>>>>>>> on
>>>>>>>> Monday.
>>>>>>>> What’s “matrix” config? Shouldn’t we just replicate the same jobs on
>>>>>> the
>>>>>>>> new instance?
>>>>>>>> 
>>>>>>>> 
>>>>>>> Not sure on the exact name/feature but "matrix" is basically the
>>>>> ability
>>>>>> to
>>>>>>> say "run this build/test across a set of JDK versions" rather than a
>>>>>> single
>>>>>>> version. As a result, instead of 3 jobs for zk3.6.0, jdk 1/2/3 you end
>>>>> up
>>>>>>> with a single job which runs three times, one for each jdk type and
>>>>>>> summarizes the results. I've seen this before, I assume it's a feature
>>>>> of
>>>>>>> jenkins itself?
>>>>>>> 
>>>>>> 
>>>>>> We should use Jenkins files and this configuration will be easy and
>>>>>> committed to git
>>>>>> 
>>>>> 
>>>>> The ability to do "gitops" would be amazing!
>>>>> 
>>>> 
>>>> Yes.
>>>> But I saw on Slack that Andor already started to create new jobs.
>>>> We should do only one way in order not to waste time.
>>>> 
>>>> Andor can you please share your work?
>>>> Thanks for doing it
>>>> 
>>>> Enrico
>>>> 
>>>> 
>>>> 
>>>>> Patrick
>>>>> 
>>>>> 
>>>>>> 
>>>>>> Enrico
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>> Patrick
>>>>>>> 
>>>>>>> 
>>>>>>>> Andor
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>>> On 2020. Jul 17., at 2:51, Patrick Hunt <ph...@apache.org> wrote:
>>>>>>>>> 
>>>>>>>>> I updated the job I linked earlier based on what's the latest on
>>>>> the
>>>>>>>> legacy
>>>>>>>>> jenkins. It ran successfully
>>>>>>>>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
>>>>>>>>> 
>>>>>>>>> I didn't replicate every config setting - main gap is the spotbugs
>>>>>>>>> post-build, which seems to be missing from the new jenkins plugins.
>>>>>>>>> 
>>>>>>>>> That's just maven master though. Not sure about the rest. Can we do
>>>>>>> more
>>>>>>>> of
>>>>>>>>> a "matrix" config in the new system vs cloning all the time?
>>>>>>>>> 
>>>>>>>>> Patrick
>>>>>>>>> 
>>>>>>>>> On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt <ph...@apache.org>
>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt <ph...@apache.org>
>>>>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <
>>>>>>> eolivelli@gmail.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>> 
>>>>>>>>>>>> FYI
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> Fun. I do notice it says "Hadoop and related projects have their
>>>>>> own
>>>>>>>>>>> migration path to follow" - any insight on that? We are or are
>>>>> not
>>>>>>>> lumped
>>>>>>>>>>> in? I would assume we are?
>>>>>>>>>>> 
>>>>>>>>>>> This (eventual migration) came up a while back on the Hadoop PMC
>>>>>> and
>>>>>>> I
>>>>>>>>>>> volunteered to try for us (ZK). I was never able to get it to
>>>>>> work, I
>>>>>>>>>>> provided feedback to infra  but they never got back, as such we
>>>>>> have
>>>>>>> a
>>>>>>>>>>> project here that's not working with some basic dependencies
>>>>>> missing:
>>>>>>>>>>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/
>>>>>>>>>>> 
>>>>>>>>>>> That said, we can try again. Can we verify where ZK is supposed
>>>>> to
>>>>>>>> land?
>>>>>>>>>>> Perhaps we can try to delete and recreate the POC job I created
>>>>> at
>>>>>>> that
>>>>>>>>>>> link to see if we can get it working?
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>> I see another email thread on the list saying that we are part of
>>>>>> said
>>>>>>>>>> "related projects". We are expected to move to
>>>>>>>>>> http://ci-hadoop.apache.org/ within 4 weeks. Seems nodes are
>>>>>> already
>>>>>>>>>> being removed/migrated from the "H#" pool.
>>>>>>>>>> 
>>>>>>>>>> Also this:
>>>>>>>>>> 
>>>>>>>>>> There are over 400 plugins on the current builds.apache.org -
>>>>> most
>>>>>> of
>>>>>>>> which
>>>>>>>>>> we don't need any more, or are replaced with different plugins on
>>>>>> the
>>>>>>>> new
>>>>>>>>>> system. I expect there may be some plugins we still need to
>>>>> install
>>>>>> to
>>>>>>>> get
>>>>>>>>>> you going again, which is why it is vitally important that you
>>>>> start
>>>>>>>>>> testing and migrating your jobs over *now*. You should all have
>>>>>> auth.
>>>>>>>>>> 
>>>>>>>>>> Any questions, feel free to email the
>>>>> hadoop-migrations@apache.org
>>>>>>>> list if
>>>>>>>>>> you are one of the projects listed below. The rest of you, not
>>>>>>> listed, a
>>>>>>>>>> similar email to this one will be posted for you shortly on
>>>>>>> builds@a.o.
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> full details
>>>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>> https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
>>>>>>>>>> 
>>>>>>>>>> Patrick
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>>> Patrick
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> ---------- Forwarded message ---------
>>>>>>>>>>>> Da: Gavin McDonald <gm...@apache.org>
>>>>>>>>>>>> Date: Gio 16 Lug 2020, 18:33
>>>>>>>>>>>> Subject: [IMPORTANT] - Migration to ci-builds.a.o
>>>>>>>>>>>> To: builds <bu...@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 Andor Molnar <an...@apache.org>.

Where’s that example…?



> On 2020. Jul 20., at 20:02, Enrico Olivelli <eo...@gmail.com> wrote:
> 
> Il Lun 20 Lug 2020, 19:40 Andor Molnar <an...@apache.org> ha scritto:
> 
>> Hi Enrico,
>> 
>> No worries, I only created a few jobs to make some progress, but feel free
>> to ignore that and do it in a better way. The “View” or “Folder” that I was
>> adding jobs is
>> 
>> https://ci-hadoop.apache.org/view/ZooKeeper/
>> 
>> 
>> Andor
>> 
> 
> This is an example from Apache Maven  project. It is very complex because
> tests are in another repo and for lots if other reasons. We just have to
> create a simpler file.
> 
> If nobody volunteers I can try to spend some time but I won't have a fast
> pace these weeks
> 
> 
> Enrico
> 
> 
> 
>> 
>> 
>>> On 2020. Jul 20., at 19:34, Enrico Olivelli <eo...@gmail.com> wrote:
>>> 
>>> Il Lun 20 Lug 2020, 19:02 Patrick Hunt <ph...@apache.org> ha scritto:
>>> 
>>>> On Mon, Jul 20, 2020 at 9:47 AM Enrico Olivelli <eo...@gmail.com>
>>>> wrote:
>>>> 
>>>>> Il Lun 20 Lug 2020, 18:41 Patrick Hunt <ph...@apache.org> ha scritto:
>>>>> 
>>>>>> On Sat, Jul 18, 2020 at 12:20 PM Andor Molnar <an...@apache.org>
>>>> wrote:
>>>>>> 
>>>>>>> Hi Pat,
>>>>>>> 
>>>>>>> I have admin rights in the new system too and probably can work on
>>>> this
>>>>>> on
>>>>>>> Monday.
>>>>>>> What’s “matrix” config? Shouldn’t we just replicate the same jobs on
>>>>> the
>>>>>>> new instance?
>>>>>>> 
>>>>>>> 
>>>>>> Not sure on the exact name/feature but "matrix" is basically the
>>>> ability
>>>>> to
>>>>>> say "run this build/test across a set of JDK versions" rather than a
>>>>> single
>>>>>> version. As a result, instead of 3 jobs for zk3.6.0, jdk 1/2/3 you end
>>>> up
>>>>>> with a single job which runs three times, one for each jdk type and
>>>>>> summarizes the results. I've seen this before, I assume it's a feature
>>>> of
>>>>>> jenkins itself?
>>>>>> 
>>>>> 
>>>>> We should use Jenkins files and this configuration will be easy and
>>>>> committed to git
>>>>> 
>>>> 
>>>> The ability to do "gitops" would be amazing!
>>>> 
>>> 
>>> Yes.
>>> But I saw on Slack that Andor already started to create new jobs.
>>> We should do only one way in order not to waste time.
>>> 
>>> Andor can you please share your work?
>>> Thanks for doing it
>>> 
>>> Enrico
>>> 
>>> 
>>> 
>>>> Patrick
>>>> 
>>>> 
>>>>> 
>>>>> Enrico
>>>>> 
>>>>> 
>>>>> 
>>>>>> Patrick
>>>>>> 
>>>>>> 
>>>>>>> Andor
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>>> On 2020. Jul 17., at 2:51, Patrick Hunt <ph...@apache.org> wrote:
>>>>>>>> 
>>>>>>>> I updated the job I linked earlier based on what's the latest on
>>>> the
>>>>>>> legacy
>>>>>>>> jenkins. It ran successfully
>>>>>>>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
>>>>>>>> 
>>>>>>>> I didn't replicate every config setting - main gap is the spotbugs
>>>>>>>> post-build, which seems to be missing from the new jenkins plugins.
>>>>>>>> 
>>>>>>>> That's just maven master though. Not sure about the rest. Can we do
>>>>>> more
>>>>>>> of
>>>>>>>> a "matrix" config in the new system vs cloning all the time?
>>>>>>>> 
>>>>>>>> Patrick
>>>>>>>> 
>>>>>>>> On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt <ph...@apache.org>
>>>>> wrote:
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt <ph...@apache.org>
>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <
>>>>>> eolivelli@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>>> FYI
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> Fun. I do notice it says "Hadoop and related projects have their
>>>>> own
>>>>>>>>>> migration path to follow" - any insight on that? We are or are
>>>> not
>>>>>>> lumped
>>>>>>>>>> in? I would assume we are?
>>>>>>>>>> 
>>>>>>>>>> This (eventual migration) came up a while back on the Hadoop PMC
>>>>> and
>>>>>> I
>>>>>>>>>> volunteered to try for us (ZK). I was never able to get it to
>>>>> work, I
>>>>>>>>>> provided feedback to infra  but they never got back, as such we
>>>>> have
>>>>>> a
>>>>>>>>>> project here that's not working with some basic dependencies
>>>>> missing:
>>>>>>>>>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/
>>>>>>>>>> 
>>>>>>>>>> That said, we can try again. Can we verify where ZK is supposed
>>>> to
>>>>>>> land?
>>>>>>>>>> Perhaps we can try to delete and recreate the POC job I created
>>>> at
>>>>>> that
>>>>>>>>>> link to see if we can get it working?
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> I see another email thread on the list saying that we are part of
>>>>> said
>>>>>>>>> "related projects". We are expected to move to
>>>>>>>>> http://ci-hadoop.apache.org/ within 4 weeks. Seems nodes are
>>>>> already
>>>>>>>>> being removed/migrated from the "H#" pool.
>>>>>>>>> 
>>>>>>>>> Also this:
>>>>>>>>> 
>>>>>>>>> There are over 400 plugins on the current builds.apache.org -
>>>> most
>>>>> of
>>>>>>> which
>>>>>>>>> we don't need any more, or are replaced with different plugins on
>>>>> the
>>>>>>> new
>>>>>>>>> system. I expect there may be some plugins we still need to
>>>> install
>>>>> to
>>>>>>> get
>>>>>>>>> you going again, which is why it is vitally important that you
>>>> start
>>>>>>>>> testing and migrating your jobs over *now*. You should all have
>>>>> auth.
>>>>>>>>> 
>>>>>>>>> Any questions, feel free to email the
>>>> hadoop-migrations@apache.org
>>>>>>> list if
>>>>>>>>> you are one of the projects listed below. The rest of you, not
>>>>>> listed, a
>>>>>>>>> similar email to this one will be posted for you shortly on
>>>>>> builds@a.o.
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> full details
>>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>> https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
>>>>>>>>> 
>>>>>>>>> Patrick
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> Patrick
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> ---------- Forwarded message ---------
>>>>>>>>>>> Da: Gavin McDonald <gm...@apache.org>
>>>>>>>>>>> Date: Gio 16 Lug 2020, 18:33
>>>>>>>>>>> Subject: [IMPORTANT] - Migration to ci-builds.a.o
>>>>>>>>>>> To: builds <bu...@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 Enrico Olivelli <eo...@gmail.com>.

Il Lun 20 Lug 2020, 19:40 Andor Molnar <an...@apache.org> ha scritto:

> Hi Enrico,
>
> No worries, I only created a few jobs to make some progress, but feel free
> to ignore that and do it in a better way. The “View” or “Folder” that I was
> adding jobs is
>
> https://ci-hadoop.apache.org/view/ZooKeeper/
>
>
> Andor
>

This is an example from Apache Maven  project. It is very complex because
tests are in another repo and for lots if other reasons. We just have to
create a simpler file.

If nobody volunteers I can try to spend some time but I won't have a fast
pace these weeks


Enrico



>
>
> > On 2020. Jul 20., at 19:34, Enrico Olivelli <eo...@gmail.com> wrote:
> >
> > Il Lun 20 Lug 2020, 19:02 Patrick Hunt <ph...@apache.org> ha scritto:
> >
> >> On Mon, Jul 20, 2020 at 9:47 AM Enrico Olivelli <eo...@gmail.com>
> >> wrote:
> >>
> >>> Il Lun 20 Lug 2020, 18:41 Patrick Hunt <ph...@apache.org> ha scritto:
> >>>
> >>>> On Sat, Jul 18, 2020 at 12:20 PM Andor Molnar <an...@apache.org>
> >> wrote:
> >>>>
> >>>>> Hi Pat,
> >>>>>
> >>>>> I have admin rights in the new system too and probably can work on
> >> this
> >>>> on
> >>>>> Monday.
> >>>>> What’s “matrix” config? Shouldn’t we just replicate the same jobs on
> >>> the
> >>>>> new instance?
> >>>>>
> >>>>>
> >>>> Not sure on the exact name/feature but "matrix" is basically the
> >> ability
> >>> to
> >>>> say "run this build/test across a set of JDK versions" rather than a
> >>> single
> >>>> version. As a result, instead of 3 jobs for zk3.6.0, jdk 1/2/3 you end
> >> up
> >>>> with a single job which runs three times, one for each jdk type and
> >>>> summarizes the results. I've seen this before, I assume it's a feature
> >> of
> >>>> jenkins itself?
> >>>>
> >>>
> >>> We should use Jenkins files and this configuration will be easy and
> >>> committed to git
> >>>
> >>
> >> The ability to do "gitops" would be amazing!
> >>
> >
> > Yes.
> > But I saw on Slack that Andor already started to create new jobs.
> > We should do only one way in order not to waste time.
> >
> > Andor can you please share your work?
> > Thanks for doing it
> >
> > Enrico
> >
> >
> >
> >> Patrick
> >>
> >>
> >>>
> >>> Enrico
> >>>
> >>>
> >>>
> >>>> Patrick
> >>>>
> >>>>
> >>>>> Andor
> >>>>>
> >>>>>
> >>>>>
> >>>>>> On 2020. Jul 17., at 2:51, Patrick Hunt <ph...@apache.org> wrote:
> >>>>>>
> >>>>>> I updated the job I linked earlier based on what's the latest on
> >> the
> >>>>> legacy
> >>>>>> jenkins. It ran successfully
> >>>>>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
> >>>>>>
> >>>>>> I didn't replicate every config setting - main gap is the spotbugs
> >>>>>> post-build, which seems to be missing from the new jenkins plugins.
> >>>>>>
> >>>>>> That's just maven master though. Not sure about the rest. Can we do
> >>>> more
> >>>>> of
> >>>>>> a "matrix" config in the new system vs cloning all the time?
> >>>>>>
> >>>>>> Patrick
> >>>>>>
> >>>>>> On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt <ph...@apache.org>
> >>> wrote:
> >>>>>>
> >>>>>>>
> >>>>>>> On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt <ph...@apache.org>
> >>>> wrote:
> >>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <
> >>>> eolivelli@gmail.com>
> >>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> FYI
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> Fun. I do notice it says "Hadoop and related projects have their
> >>> own
> >>>>>>>> migration path to follow" - any insight on that? We are or are
> >> not
> >>>>> lumped
> >>>>>>>> in? I would assume we are?
> >>>>>>>>
> >>>>>>>> This (eventual migration) came up a while back on the Hadoop PMC
> >>> and
> >>>> I
> >>>>>>>> volunteered to try for us (ZK). I was never able to get it to
> >>> work, I
> >>>>>>>> provided feedback to infra  but they never got back, as such we
> >>> have
> >>>> a
> >>>>>>>> project here that's not working with some basic dependencies
> >>> missing:
> >>>>>>>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/
> >>>>>>>>
> >>>>>>>> That said, we can try again. Can we verify where ZK is supposed
> >> to
> >>>>> land?
> >>>>>>>> Perhaps we can try to delete and recreate the POC job I created
> >> at
> >>>> that
> >>>>>>>> link to see if we can get it working?
> >>>>>>>>
> >>>>>>>>
> >>>>>>> I see another email thread on the list saying that we are part of
> >>> said
> >>>>>>> "related projects". We are expected to move to
> >>>>>>> http://ci-hadoop.apache.org/ within 4 weeks. Seems nodes are
> >>> already
> >>>>>>> being removed/migrated from the "H#" pool.
> >>>>>>>
> >>>>>>> Also this:
> >>>>>>>
> >>>>>>> There are over 400 plugins on the current builds.apache.org -
> >> most
> >>> of
> >>>>> which
> >>>>>>> we don't need any more, or are replaced with different plugins on
> >>> the
> >>>>> new
> >>>>>>> system. I expect there may be some plugins we still need to
> >> install
> >>> to
> >>>>> get
> >>>>>>> you going again, which is why it is vitally important that you
> >> start
> >>>>>>> testing and migrating your jobs over *now*. You should all have
> >>> auth.
> >>>>>>>
> >>>>>>> Any questions, feel free to email the
> >> hadoop-migrations@apache.org
> >>>>> list if
> >>>>>>> you are one of the projects listed below. The rest of you, not
> >>>> listed, a
> >>>>>>> similar email to this one will be posted for you shortly on
> >>>> builds@a.o.
> >>>>>>>
> >>>>>>>
> >>>>>>> full details
> >>>>>>>
> >>>>>
> >>>>
> >>>
> >>
> https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
> >>>>>>>
> >>>>>>> Patrick
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>> Patrick
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>>
> >>>>>>>>> ---------- Forwarded message ---------
> >>>>>>>>> Da: Gavin McDonald <gm...@apache.org>
> >>>>>>>>> Date: Gio 16 Lug 2020, 18:33
> >>>>>>>>> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> >>>>>>>>> To: builds <bu...@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 Andor Molnar <an...@apache.org>.

Hi Enrico,

No worries, I only created a few jobs to make some progress, but feel free to ignore that and do it in a better way. The “View” or “Folder” that I was adding jobs is 

https://ci-hadoop.apache.org/view/ZooKeeper/

Andor



> On 2020. Jul 20., at 19:34, Enrico Olivelli <eo...@gmail.com> wrote:
> 
> Il Lun 20 Lug 2020, 19:02 Patrick Hunt <ph...@apache.org> ha scritto:
> 
>> On Mon, Jul 20, 2020 at 9:47 AM Enrico Olivelli <eo...@gmail.com>
>> wrote:
>> 
>>> Il Lun 20 Lug 2020, 18:41 Patrick Hunt <ph...@apache.org> ha scritto:
>>> 
>>>> On Sat, Jul 18, 2020 at 12:20 PM Andor Molnar <an...@apache.org>
>> wrote:
>>>> 
>>>>> Hi Pat,
>>>>> 
>>>>> I have admin rights in the new system too and probably can work on
>> this
>>>> on
>>>>> Monday.
>>>>> What’s “matrix” config? Shouldn’t we just replicate the same jobs on
>>> the
>>>>> new instance?
>>>>> 
>>>>> 
>>>> Not sure on the exact name/feature but "matrix" is basically the
>> ability
>>> to
>>>> say "run this build/test across a set of JDK versions" rather than a
>>> single
>>>> version. As a result, instead of 3 jobs for zk3.6.0, jdk 1/2/3 you end
>> up
>>>> with a single job which runs three times, one for each jdk type and
>>>> summarizes the results. I've seen this before, I assume it's a feature
>> of
>>>> jenkins itself?
>>>> 
>>> 
>>> We should use Jenkins files and this configuration will be easy and
>>> committed to git
>>> 
>> 
>> The ability to do "gitops" would be amazing!
>> 
> 
> Yes.
> But I saw on Slack that Andor already started to create new jobs.
> We should do only one way in order not to waste time.
> 
> Andor can you please share your work?
> Thanks for doing it
> 
> Enrico
> 
> 
> 
>> Patrick
>> 
>> 
>>> 
>>> Enrico
>>> 
>>> 
>>> 
>>>> Patrick
>>>> 
>>>> 
>>>>> Andor
>>>>> 
>>>>> 
>>>>> 
>>>>>> On 2020. Jul 17., at 2:51, Patrick Hunt <ph...@apache.org> wrote:
>>>>>> 
>>>>>> I updated the job I linked earlier based on what's the latest on
>> the
>>>>> legacy
>>>>>> jenkins. It ran successfully
>>>>>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
>>>>>> 
>>>>>> I didn't replicate every config setting - main gap is the spotbugs
>>>>>> post-build, which seems to be missing from the new jenkins plugins.
>>>>>> 
>>>>>> That's just maven master though. Not sure about the rest. Can we do
>>>> more
>>>>> of
>>>>>> a "matrix" config in the new system vs cloning all the time?
>>>>>> 
>>>>>> Patrick
>>>>>> 
>>>>>> On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt <ph...@apache.org>
>>> wrote:
>>>>>> 
>>>>>>> 
>>>>>>> On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt <ph...@apache.org>
>>>> wrote:
>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <
>>>> eolivelli@gmail.com>
>>>>>>>> wrote:
>>>>>>>> 
>>>>>>>>> FYI
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> Fun. I do notice it says "Hadoop and related projects have their
>>> own
>>>>>>>> migration path to follow" - any insight on that? We are or are
>> not
>>>>> lumped
>>>>>>>> in? I would assume we are?
>>>>>>>> 
>>>>>>>> This (eventual migration) came up a while back on the Hadoop PMC
>>> and
>>>> I
>>>>>>>> volunteered to try for us (ZK). I was never able to get it to
>>> work, I
>>>>>>>> provided feedback to infra  but they never got back, as such we
>>> have
>>>> a
>>>>>>>> project here that's not working with some basic dependencies
>>> missing:
>>>>>>>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/
>>>>>>>> 
>>>>>>>> That said, we can try again. Can we verify where ZK is supposed
>> to
>>>>> land?
>>>>>>>> Perhaps we can try to delete and recreate the POC job I created
>> at
>>>> that
>>>>>>>> link to see if we can get it working?
>>>>>>>> 
>>>>>>>> 
>>>>>>> I see another email thread on the list saying that we are part of
>>> said
>>>>>>> "related projects". We are expected to move to
>>>>>>> http://ci-hadoop.apache.org/ within 4 weeks. Seems nodes are
>>> already
>>>>>>> being removed/migrated from the "H#" pool.
>>>>>>> 
>>>>>>> Also this:
>>>>>>> 
>>>>>>> There are over 400 plugins on the current builds.apache.org -
>> most
>>> of
>>>>> which
>>>>>>> we don't need any more, or are replaced with different plugins on
>>> the
>>>>> new
>>>>>>> system. I expect there may be some plugins we still need to
>> install
>>> to
>>>>> get
>>>>>>> you going again, which is why it is vitally important that you
>> start
>>>>>>> testing and migrating your jobs over *now*. You should all have
>>> auth.
>>>>>>> 
>>>>>>> Any questions, feel free to email the
>> hadoop-migrations@apache.org
>>>>> list if
>>>>>>> you are one of the projects listed below. The rest of you, not
>>>> listed, a
>>>>>>> similar email to this one will be posted for you shortly on
>>>> builds@a.o.
>>>>>>> 
>>>>>>> 
>>>>>>> full details
>>>>>>> 
>>>>> 
>>>> 
>>> 
>> https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
>>>>>>> 
>>>>>>> Patrick
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>>> Patrick
>>>>>>>> 
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> ---------- Forwarded message ---------
>>>>>>>>> Da: Gavin McDonald <gm...@apache.org>
>>>>>>>>> Date: Gio 16 Lug 2020, 18:33
>>>>>>>>> Subject: [IMPORTANT] - Migration to ci-builds.a.o
>>>>>>>>> To: builds <bu...@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 Enrico Olivelli <eo...@gmail.com>.

Il Lun 20 Lug 2020, 19:02 Patrick Hunt <ph...@apache.org> ha scritto:

> On Mon, Jul 20, 2020 at 9:47 AM Enrico Olivelli <eo...@gmail.com>
> wrote:
>
> > Il Lun 20 Lug 2020, 18:41 Patrick Hunt <ph...@apache.org> ha scritto:
> >
> > > On Sat, Jul 18, 2020 at 12:20 PM Andor Molnar <an...@apache.org>
> wrote:
> > >
> > > > Hi Pat,
> > > >
> > > > I have admin rights in the new system too and probably can work on
> this
> > > on
> > > > Monday.
> > > > What’s “matrix” config? Shouldn’t we just replicate the same jobs on
> > the
> > > > new instance?
> > > >
> > > >
> > > Not sure on the exact name/feature but "matrix" is basically the
> ability
> > to
> > > say "run this build/test across a set of JDK versions" rather than a
> > single
> > > version. As a result, instead of 3 jobs for zk3.6.0, jdk 1/2/3 you end
> up
> > > with a single job which runs three times, one for each jdk type and
> > > summarizes the results. I've seen this before, I assume it's a feature
> of
> > > jenkins itself?
> > >
> >
> > We should use Jenkins files and this configuration will be easy and
> > committed to git
> >
>
> The ability to do "gitops" would be amazing!
>

Yes.
But I saw on Slack that Andor already started to create new jobs.
We should do only one way in order not to waste time.

Andor can you please share your work?
Thanks for doing it

Enrico



> Patrick
>
>
> >
> > Enrico
> >
> >
> >
> > > Patrick
> > >
> > >
> > > > Andor
> > > >
> > > >
> > > >
> > > > > On 2020. Jul 17., at 2:51, Patrick Hunt <ph...@apache.org> wrote:
> > > > >
> > > > > I updated the job I linked earlier based on what's the latest on
> the
> > > > legacy
> > > > > jenkins. It ran successfully
> > > > > https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
> > > > >
> > > > > I didn't replicate every config setting - main gap is the spotbugs
> > > > > post-build, which seems to be missing from the new jenkins plugins.
> > > > >
> > > > > That's just maven master though. Not sure about the rest. Can we do
> > > more
> > > > of
> > > > > a "matrix" config in the new system vs cloning all the time?
> > > > >
> > > > > Patrick
> > > > >
> > > > > On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt <ph...@apache.org>
> > wrote:
> > > > >
> > > > >>
> > > > >> On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt <ph...@apache.org>
> > > wrote:
> > > > >>
> > > > >>>
> > > > >>>
> > > > >>> On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <
> > > eolivelli@gmail.com>
> > > > >>> wrote:
> > > > >>>
> > > > >>>> FYI
> > > > >>>>
> > > > >>>
> > > > >>> Fun. I do notice it says "Hadoop and related projects have their
> > own
> > > > >>> migration path to follow" - any insight on that? We are or are
> not
> > > > lumped
> > > > >>> in? I would assume we are?
> > > > >>>
> > > > >>> This (eventual migration) came up a while back on the Hadoop PMC
> > and
> > > I
> > > > >>> volunteered to try for us (ZK). I was never able to get it to
> > work, I
> > > > >>> provided feedback to infra  but they never got back, as such we
> > have
> > > a
> > > > >>> project here that's not working with some basic dependencies
> > missing:
> > > > >>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/
> > > > >>>
> > > > >>> That said, we can try again. Can we verify where ZK is supposed
> to
> > > > land?
> > > > >>> Perhaps we can try to delete and recreate the POC job I created
> at
> > > that
> > > > >>> link to see if we can get it working?
> > > > >>>
> > > > >>>
> > > > >> I see another email thread on the list saying that we are part of
> > said
> > > > >> "related projects". We are expected to move to
> > > > >> http://ci-hadoop.apache.org/ within 4 weeks. Seems nodes are
> > already
> > > > >> being removed/migrated from the "H#" pool.
> > > > >>
> > > > >> Also this:
> > > > >>
> > > > >> There are over 400 plugins on the current builds.apache.org -
> most
> > of
> > > > which
> > > > >> we don't need any more, or are replaced with different plugins on
> > the
> > > > new
> > > > >> system. I expect there may be some plugins we still need to
> install
> > to
> > > > get
> > > > >> you going again, which is why it is vitally important that you
> start
> > > > >> testing and migrating your jobs over *now*. You should all have
> > auth.
> > > > >>
> > > > >> Any questions, feel free to email the
> hadoop-migrations@apache.org
> > > > list if
> > > > >> you are one of the projects listed below. The rest of you, not
> > > listed, a
> > > > >> similar email to this one will be posted for you shortly on
> > > builds@a.o.
> > > > >>
> > > > >>
> > > > >> full details
> > > > >>
> > > >
> > >
> >
> https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
> > > > >>
> > > > >> Patrick
> > > > >>
> > > > >>
> > > > >>
> > > > >>> Patrick
> > > > >>>
> > > > >>>
> > > > >>>>
> > > > >>>> ---------- Forwarded message ---------
> > > > >>>> Da: Gavin McDonald <gm...@apache.org>
> > > > >>>> Date: Gio 16 Lug 2020, 18:33
> > > > >>>> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> > > > >>>> To: builds <bu...@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 Patrick Hunt <ph...@apache.org>.

On Mon, Jul 20, 2020 at 9:47 AM Enrico Olivelli <eo...@gmail.com> wrote:

> Il Lun 20 Lug 2020, 18:41 Patrick Hunt <ph...@apache.org> ha scritto:
>
> > On Sat, Jul 18, 2020 at 12:20 PM Andor Molnar <an...@apache.org> wrote:
> >
> > > Hi Pat,
> > >
> > > I have admin rights in the new system too and probably can work on this
> > on
> > > Monday.
> > > What’s “matrix” config? Shouldn’t we just replicate the same jobs on
> the
> > > new instance?
> > >
> > >
> > Not sure on the exact name/feature but "matrix" is basically the ability
> to
> > say "run this build/test across a set of JDK versions" rather than a
> single
> > version. As a result, instead of 3 jobs for zk3.6.0, jdk 1/2/3 you end up
> > with a single job which runs three times, one for each jdk type and
> > summarizes the results. I've seen this before, I assume it's a feature of
> > jenkins itself?
> >
>
> We should use Jenkins files and this configuration will be easy and
> committed to git
>

The ability to do "gitops" would be amazing!

Patrick


>
> Enrico
>
>
>
> > Patrick
> >
> >
> > > Andor
> > >
> > >
> > >
> > > > On 2020. Jul 17., at 2:51, Patrick Hunt <ph...@apache.org> wrote:
> > > >
> > > > I updated the job I linked earlier based on what's the latest on the
> > > legacy
> > > > jenkins. It ran successfully
> > > > https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
> > > >
> > > > I didn't replicate every config setting - main gap is the spotbugs
> > > > post-build, which seems to be missing from the new jenkins plugins.
> > > >
> > > > That's just maven master though. Not sure about the rest. Can we do
> > more
> > > of
> > > > a "matrix" config in the new system vs cloning all the time?
> > > >
> > > > Patrick
> > > >
> > > > On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt <ph...@apache.org>
> wrote:
> > > >
> > > >>
> > > >> On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt <ph...@apache.org>
> > wrote:
> > > >>
> > > >>>
> > > >>>
> > > >>> On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <
> > eolivelli@gmail.com>
> > > >>> wrote:
> > > >>>
> > > >>>> FYI
> > > >>>>
> > > >>>
> > > >>> Fun. I do notice it says "Hadoop and related projects have their
> own
> > > >>> migration path to follow" - any insight on that? We are or are not
> > > lumped
> > > >>> in? I would assume we are?
> > > >>>
> > > >>> This (eventual migration) came up a while back on the Hadoop PMC
> and
> > I
> > > >>> volunteered to try for us (ZK). I was never able to get it to
> work, I
> > > >>> provided feedback to infra  but they never got back, as such we
> have
> > a
> > > >>> project here that's not working with some basic dependencies
> missing:
> > > >>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/
> > > >>>
> > > >>> That said, we can try again. Can we verify where ZK is supposed to
> > > land?
> > > >>> Perhaps we can try to delete and recreate the POC job I created at
> > that
> > > >>> link to see if we can get it working?
> > > >>>
> > > >>>
> > > >> I see another email thread on the list saying that we are part of
> said
> > > >> "related projects". We are expected to move to
> > > >> http://ci-hadoop.apache.org/ within 4 weeks. Seems nodes are
> already
> > > >> being removed/migrated from the "H#" pool.
> > > >>
> > > >> Also this:
> > > >>
> > > >> There are over 400 plugins on the current builds.apache.org - most
> of
> > > which
> > > >> we don't need any more, or are replaced with different plugins on
> the
> > > new
> > > >> system. I expect there may be some plugins we still need to install
> to
> > > get
> > > >> you going again, which is why it is vitally important that you start
> > > >> testing and migrating your jobs over *now*. You should all have
> auth.
> > > >>
> > > >> Any questions, feel free to email the hadoop-migrations@apache.org
> > > list if
> > > >> you are one of the projects listed below. The rest of you, not
> > listed, a
> > > >> similar email to this one will be posted for you shortly on
> > builds@a.o.
> > > >>
> > > >>
> > > >> full details
> > > >>
> > >
> >
> https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
> > > >>
> > > >> Patrick
> > > >>
> > > >>
> > > >>
> > > >>> Patrick
> > > >>>
> > > >>>
> > > >>>>
> > > >>>> ---------- Forwarded message ---------
> > > >>>> Da: Gavin McDonald <gm...@apache.org>
> > > >>>> Date: Gio 16 Lug 2020, 18:33
> > > >>>> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> > > >>>> To: builds <bu...@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 Enrico Olivelli <eo...@gmail.com>.

Il Lun 20 Lug 2020, 18:41 Patrick Hunt <ph...@apache.org> ha scritto:

> On Sat, Jul 18, 2020 at 12:20 PM Andor Molnar <an...@apache.org> wrote:
>
> > Hi Pat,
> >
> > I have admin rights in the new system too and probably can work on this
> on
> > Monday.
> > What’s “matrix” config? Shouldn’t we just replicate the same jobs on the
> > new instance?
> >
> >
> Not sure on the exact name/feature but "matrix" is basically the ability to
> say "run this build/test across a set of JDK versions" rather than a single
> version. As a result, instead of 3 jobs for zk3.6.0, jdk 1/2/3 you end up
> with a single job which runs three times, one for each jdk type and
> summarizes the results. I've seen this before, I assume it's a feature of
> jenkins itself?
>

We should use Jenkins files and this configuration will be easy and
committed to git

Enrico



> Patrick
>
>
> > Andor
> >
> >
> >
> > > On 2020. Jul 17., at 2:51, Patrick Hunt <ph...@apache.org> wrote:
> > >
> > > I updated the job I linked earlier based on what's the latest on the
> > legacy
> > > jenkins. It ran successfully
> > > https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
> > >
> > > I didn't replicate every config setting - main gap is the spotbugs
> > > post-build, which seems to be missing from the new jenkins plugins.
> > >
> > > That's just maven master though. Not sure about the rest. Can we do
> more
> > of
> > > a "matrix" config in the new system vs cloning all the time?
> > >
> > > Patrick
> > >
> > > On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt <ph...@apache.org> wrote:
> > >
> > >>
> > >> On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt <ph...@apache.org>
> wrote:
> > >>
> > >>>
> > >>>
> > >>> On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <
> eolivelli@gmail.com>
> > >>> wrote:
> > >>>
> > >>>> FYI
> > >>>>
> > >>>
> > >>> Fun. I do notice it says "Hadoop and related projects have their own
> > >>> migration path to follow" - any insight on that? We are or are not
> > lumped
> > >>> in? I would assume we are?
> > >>>
> > >>> This (eventual migration) came up a while back on the Hadoop PMC and
> I
> > >>> volunteered to try for us (ZK). I was never able to get it to work, I
> > >>> provided feedback to infra  but they never got back, as such we have
> a
> > >>> project here that's not working with some basic dependencies missing:
> > >>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/
> > >>>
> > >>> That said, we can try again. Can we verify where ZK is supposed to
> > land?
> > >>> Perhaps we can try to delete and recreate the POC job I created at
> that
> > >>> link to see if we can get it working?
> > >>>
> > >>>
> > >> I see another email thread on the list saying that we are part of said
> > >> "related projects". We are expected to move to
> > >> http://ci-hadoop.apache.org/ within 4 weeks. Seems nodes are already
> > >> being removed/migrated from the "H#" pool.
> > >>
> > >> Also this:
> > >>
> > >> There are over 400 plugins on the current builds.apache.org - most of
> > which
> > >> we don't need any more, or are replaced with different plugins on the
> > new
> > >> system. I expect there may be some plugins we still need to install to
> > get
> > >> you going again, which is why it is vitally important that you start
> > >> testing and migrating your jobs over *now*. You should all have auth.
> > >>
> > >> Any questions, feel free to email the hadoop-migrations@apache.org
> > list if
> > >> you are one of the projects listed below. The rest of you, not
> listed, a
> > >> similar email to this one will be posted for you shortly on
> builds@a.o.
> > >>
> > >>
> > >> full details
> > >>
> >
> https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
> > >>
> > >> Patrick
> > >>
> > >>
> > >>
> > >>> Patrick
> > >>>
> > >>>
> > >>>>
> > >>>> ---------- Forwarded message ---------
> > >>>> Da: Gavin McDonald <gm...@apache.org>
> > >>>> Date: Gio 16 Lug 2020, 18:33
> > >>>> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> > >>>> To: builds <bu...@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 Patrick Hunt <ph...@apache.org>.

On Sat, Jul 18, 2020 at 12:20 PM Andor Molnar <an...@apache.org> wrote:

> Hi Pat,
>
> I have admin rights in the new system too and probably can work on this on
> Monday.
> What’s “matrix” config? Shouldn’t we just replicate the same jobs on the
> new instance?
>
>
Not sure on the exact name/feature but "matrix" is basically the ability to
say "run this build/test across a set of JDK versions" rather than a single
version. As a result, instead of 3 jobs for zk3.6.0, jdk 1/2/3 you end up
with a single job which runs three times, one for each jdk type and
summarizes the results. I've seen this before, I assume it's a feature of
jenkins itself?

Patrick


> Andor
>
>
>
> > On 2020. Jul 17., at 2:51, Patrick Hunt <ph...@apache.org> wrote:
> >
> > I updated the job I linked earlier based on what's the latest on the
> legacy
> > jenkins. It ran successfully
> > https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
> >
> > I didn't replicate every config setting - main gap is the spotbugs
> > post-build, which seems to be missing from the new jenkins plugins.
> >
> > That's just maven master though. Not sure about the rest. Can we do more
> of
> > a "matrix" config in the new system vs cloning all the time?
> >
> > Patrick
> >
> > On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt <ph...@apache.org> wrote:
> >
> >>
> >> On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt <ph...@apache.org> wrote:
> >>
> >>>
> >>>
> >>> On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <eo...@gmail.com>
> >>> wrote:
> >>>
> >>>> FYI
> >>>>
> >>>
> >>> Fun. I do notice it says "Hadoop and related projects have their own
> >>> migration path to follow" - any insight on that? We are or are not
> lumped
> >>> in? I would assume we are?
> >>>
> >>> This (eventual migration) came up a while back on the Hadoop PMC and I
> >>> volunteered to try for us (ZK). I was never able to get it to work, I
> >>> provided feedback to infra  but they never got back, as such we have a
> >>> project here that's not working with some basic dependencies missing:
> >>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/
> >>>
> >>> That said, we can try again. Can we verify where ZK is supposed to
> land?
> >>> Perhaps we can try to delete and recreate the POC job I created at that
> >>> link to see if we can get it working?
> >>>
> >>>
> >> I see another email thread on the list saying that we are part of said
> >> "related projects". We are expected to move to
> >> http://ci-hadoop.apache.org/ within 4 weeks. Seems nodes are already
> >> being removed/migrated from the "H#" pool.
> >>
> >> Also this:
> >>
> >> There are over 400 plugins on the current builds.apache.org - most of
> which
> >> we don't need any more, or are replaced with different plugins on the
> new
> >> system. I expect there may be some plugins we still need to install to
> get
> >> you going again, which is why it is vitally important that you start
> >> testing and migrating your jobs over *now*. You should all have auth.
> >>
> >> Any questions, feel free to email the hadoop-migrations@apache.org
> list if
> >> you are one of the projects listed below. The rest of you, not listed, a
> >> similar email to this one will be posted for you shortly on builds@a.o.
> >>
> >>
> >> full details
> >>
> https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
> >>
> >> Patrick
> >>
> >>
> >>
> >>> Patrick
> >>>
> >>>
> >>>>
> >>>> ---------- Forwarded message ---------
> >>>> Da: Gavin McDonald <gm...@apache.org>
> >>>> Date: Gio 16 Lug 2020, 18:33
> >>>> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> >>>> To: builds <bu...@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 Andor Molnar <an...@apache.org>.

There's one thing I noticed is that the summary of each build is
missing from the build's status page. It's probably caused by a missing
Jenkins plugin, but I don't know. Build preferences are roughly the
same.

Andor



On Mon, 2020-07-20 at 15:48 +0200, Andor Molnar wrote:
> Hi,
> 
> I created a few new jobs based on your suggestions. Before going
> forward please take a look at them.
> 
> I created Jdk LTS jobs (8 and 11) for all active branches: 3.5, 3.6
> and
> master. Also added the Maven option surefire.forkcount=4 to all jobs
> to
> limit the number of concurrent threads in unit tests.
> 
> Do you think we also need non-LTS Java build jobs too?
> 
> https://ci-hadoop.apache.org/view/ZooKeeper/
> 
> Andor
> 
> 
> 
> On Sun, 2020-07-19 at 07:50 +0200, Enrico Olivelli wrote:
> > Il Sab 18 Lug 2020, 21:20 Andor Molnar <an...@apache.org> ha
> > scritto:
> > 
> > > Hi Pat,
> > > 
> > > I have admin rights in the new system too and probably can work
> > > on
> > > this on
> > > Monday.
> > > What’s “matrix” config? Shouldn’t we just replicate the same jobs
> > > on the
> > > new instance?
> > > 
> > 
> > This is my list of important jobs:
> > - maven builds of master against every supported jdk +EA (for JDK
> > outreach
> > quality program)
> > - maven build of master on windows on jdk8
> > - maven build of branch-3.5 and branch-3.6
> > - ant build of branch-3.5 on jdk8
> > - maven precommit job
> > 
> > Enrico
> > 
> > 
> > > Andor
> > > 
> > > 
> > > 
> > > > On 2020. Jul 17., at 2:51, Patrick Hunt <ph...@apache.org>
> > > > wrote:
> > > > 
> > > > I updated the job I linked earlier based on what's the latest
> > > > on
> > > > the
> > > legacy
> > > > jenkins. It ran successfully
> > > > https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
> > > > 
> > > > I didn't replicate every config setting - main gap is the
> > > > spotbugs
> > > > post-build, which seems to be missing from the new jenkins
> > > > plugins.
> > > > 
> > > > That's just maven master though. Not sure about the rest. Can
> > > > we
> > > > do more
> > > of
> > > > a "matrix" config in the new system vs cloning all the time?
> > > > 
> > > > Patrick
> > > > 
> > > > On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt <ph...@apache.org>
> > > > wrote:
> > > > 
> > > > > On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt <
> > > > > phunt@apache.org>
> > > > > wrote:
> > > > > 
> > > > > > On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <
> > > > > > eolivelli@gmail.com>
> > > > > > wrote:
> > > > > > 
> > > > > > > FYI
> > > > > > > 
> > > > > > 
> > > > > > Fun. I do notice it says "Hadoop and related projects have
> > > > > > their own
> > > > > > migration path to follow" - any insight on that? We are or
> > > > > > are not
> > > lumped
> > > > > > in? I would assume we are?
> > > > > > 
> > > > > > This (eventual migration) came up a while back on the
> > > > > > Hadoop
> > > > > > PMC and I
> > > > > > volunteered to try for us (ZK). I was never able to get it
> > > > > > to
> > > > > > work, I
> > > > > > provided feedback to infra  but they never got back, as
> > > > > > such
> > > > > > we have a
> > > > > > project here that's not working with some basic
> > > > > > dependencies
> > > > > > missing:
> > > > > > https://ci-hadoop.apache.org/job/zookeeper-master-maven/
> > > > > > 
> > > > > > That said, we can try again. Can we verify where ZK is
> > > > > > supposed to
> > > land?
> > > > > > Perhaps we can try to delete and recreate the POC job I
> > > > > > created at that
> > > > > > link to see if we can get it working?
> > > > > > 
> > > > > > 
> > > > > I see another email thread on the list saying that we are
> > > > > part
> > > > > of said
> > > > > "related projects". We are expected to move to
> > > > > http://ci-hadoop.apache.org/ within 4 weeks. Seems nodes are
> > > > > already
> > > > > being removed/migrated from the "H#" pool.
> > > > > 
> > > > > Also this:
> > > > > 
> > > > > There are over 400 plugins on the current builds.apache.org -
> > > > > most of
> > > which
> > > > > we don't need any more, or are replaced with different
> > > > > plugins
> > > > > on the
> > > new
> > > > > system. I expect there may be some plugins we still need to
> > > > > install to
> > > get
> > > > > you going again, which is why it is vitally important that
> > > > > you
> > > > > start
> > > > > testing and migrating your jobs over *now*. You should all
> > > > > have
> > > > > auth.
> > > > > 
> > > > > Any questions, feel free to email the 
> > > > > hadoop-migrations@apache.org
> > > list if
> > > > > you are one of the projects listed below. The rest of you,
> > > > > not
> > > > > listed, a
> > > > > similar email to this one will be posted for you shortly on 
> > > > > builds@a.o.
> > > > > 
> > > > > 
> > > > > full details
> > > > > 
> > > https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
> > > > > Patrick
> > > > > 
> > > > > 
> > > > > 
> > > > > > Patrick
> > > > > > 
> > > > > > 
> > > > > > > ---------- Forwarded message ---------
> > > > > > > Da: Gavin McDonald <gm...@apache.org>
> > > > > > > Date: Gio 16 Lug 2020, 18:33
> > > > > > > Subject: [IMPORTANT] - Migration to ci-builds.a.o
> > > > > > > To: builds <bu...@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 Andor Molnar <an...@apache.org>.

Hi,

I created a few new jobs based on your suggestions. Before going
forward please take a look at them.

I created Jdk LTS jobs (8 and 11) for all active branches: 3.5, 3.6 and
master. Also added the Maven option surefire.forkcount=4 to all jobs to
limit the number of concurrent threads in unit tests.

Do you think we also need non-LTS Java build jobs too?

https://ci-hadoop.apache.org/view/ZooKeeper/

Andor



On Sun, 2020-07-19 at 07:50 +0200, Enrico Olivelli wrote:
> Il Sab 18 Lug 2020, 21:20 Andor Molnar <an...@apache.org> ha scritto:
> 
> > Hi Pat,
> > 
> > I have admin rights in the new system too and probably can work on
> > this on
> > Monday.
> > What’s “matrix” config? Shouldn’t we just replicate the same jobs
> > on the
> > new instance?
> > 
> 
> This is my list of important jobs:
> - maven builds of master against every supported jdk +EA (for JDK
> outreach
> quality program)
> - maven build of master on windows on jdk8
> - maven build of branch-3.5 and branch-3.6
> - ant build of branch-3.5 on jdk8
> - maven precommit job
> 
> Enrico
> 
> 
> > Andor
> > 
> > 
> > 
> > > On 2020. Jul 17., at 2:51, Patrick Hunt <ph...@apache.org> wrote:
> > > 
> > > I updated the job I linked earlier based on what's the latest on
> > > the
> > legacy
> > > jenkins. It ran successfully
> > > https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
> > > 
> > > I didn't replicate every config setting - main gap is the
> > > spotbugs
> > > post-build, which seems to be missing from the new jenkins
> > > plugins.
> > > 
> > > That's just maven master though. Not sure about the rest. Can we
> > > do more
> > of
> > > a "matrix" config in the new system vs cloning all the time?
> > > 
> > > Patrick
> > > 
> > > On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt <ph...@apache.org>
> > > wrote:
> > > 
> > > > On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt <ph...@apache.org>
> > > > wrote:
> > > > 
> > > > > 
> > > > > On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <
> > > > > eolivelli@gmail.com>
> > > > > wrote:
> > > > > 
> > > > > > FYI
> > > > > > 
> > > > > 
> > > > > Fun. I do notice it says "Hadoop and related projects have
> > > > > their own
> > > > > migration path to follow" - any insight on that? We are or
> > > > > are not
> > lumped
> > > > > in? I would assume we are?
> > > > > 
> > > > > This (eventual migration) came up a while back on the Hadoop
> > > > > PMC and I
> > > > > volunteered to try for us (ZK). I was never able to get it to
> > > > > work, I
> > > > > provided feedback to infra  but they never got back, as such
> > > > > we have a
> > > > > project here that's not working with some basic dependencies
> > > > > missing:
> > > > > https://ci-hadoop.apache.org/job/zookeeper-master-maven/
> > > > > 
> > > > > That said, we can try again. Can we verify where ZK is
> > > > > supposed to
> > land?
> > > > > Perhaps we can try to delete and recreate the POC job I
> > > > > created at that
> > > > > link to see if we can get it working?
> > > > > 
> > > > > 
> > > > I see another email thread on the list saying that we are part
> > > > of said
> > > > "related projects". We are expected to move to
> > > > http://ci-hadoop.apache.org/ within 4 weeks. Seems nodes are
> > > > already
> > > > being removed/migrated from the "H#" pool.
> > > > 
> > > > Also this:
> > > > 
> > > > There are over 400 plugins on the current builds.apache.org -
> > > > most of
> > which
> > > > we don't need any more, or are replaced with different plugins
> > > > on the
> > new
> > > > system. I expect there may be some plugins we still need to
> > > > install to
> > get
> > > > you going again, which is why it is vitally important that you
> > > > start
> > > > testing and migrating your jobs over *now*. You should all have
> > > > auth.
> > > > 
> > > > Any questions, feel free to email the 
> > > > hadoop-migrations@apache.org
> > list if
> > > > you are one of the projects listed below. The rest of you, not
> > > > listed, a
> > > > similar email to this one will be posted for you shortly on 
> > > > builds@a.o.
> > > > 
> > > > 
> > > > full details
> > > > 
> > https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
> > > > Patrick
> > > > 
> > > > 
> > > > 
> > > > > Patrick
> > > > > 
> > > > > 
> > > > > > ---------- Forwarded message ---------
> > > > > > Da: Gavin McDonald <gm...@apache.org>
> > > > > > Date: Gio 16 Lug 2020, 18:33
> > > > > > Subject: [IMPORTANT] - Migration to ci-builds.a.o
> > > > > > To: builds <bu...@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 Enrico Olivelli <eo...@gmail.com>.

Il Sab 18 Lug 2020, 21:20 Andor Molnar <an...@apache.org> ha scritto:

> Hi Pat,
>
> I have admin rights in the new system too and probably can work on this on
> Monday.
> What’s “matrix” config? Shouldn’t we just replicate the same jobs on the
> new instance?
>

This is my list of important jobs:
- maven builds of master against every supported jdk +EA (for JDK outreach
quality program)
- maven build of master on windows on jdk8
- maven build of branch-3.5 and branch-3.6
- ant build of branch-3.5 on jdk8
- maven precommit job

Enrico


> Andor
>
>
>
> > On 2020. Jul 17., at 2:51, Patrick Hunt <ph...@apache.org> wrote:
> >
> > I updated the job I linked earlier based on what's the latest on the
> legacy
> > jenkins. It ran successfully
> > https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
> >
> > I didn't replicate every config setting - main gap is the spotbugs
> > post-build, which seems to be missing from the new jenkins plugins.
> >
> > That's just maven master though. Not sure about the rest. Can we do more
> of
> > a "matrix" config in the new system vs cloning all the time?
> >
> > Patrick
> >
> > On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt <ph...@apache.org> wrote:
> >
> >>
> >> On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt <ph...@apache.org> wrote:
> >>
> >>>
> >>>
> >>> On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <eo...@gmail.com>
> >>> wrote:
> >>>
> >>>> FYI
> >>>>
> >>>
> >>> Fun. I do notice it says "Hadoop and related projects have their own
> >>> migration path to follow" - any insight on that? We are or are not
> lumped
> >>> in? I would assume we are?
> >>>
> >>> This (eventual migration) came up a while back on the Hadoop PMC and I
> >>> volunteered to try for us (ZK). I was never able to get it to work, I
> >>> provided feedback to infra  but they never got back, as such we have a
> >>> project here that's not working with some basic dependencies missing:
> >>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/
> >>>
> >>> That said, we can try again. Can we verify where ZK is supposed to
> land?
> >>> Perhaps we can try to delete and recreate the POC job I created at that
> >>> link to see if we can get it working?
> >>>
> >>>
> >> I see another email thread on the list saying that we are part of said
> >> "related projects". We are expected to move to
> >> http://ci-hadoop.apache.org/ within 4 weeks. Seems nodes are already
> >> being removed/migrated from the "H#" pool.
> >>
> >> Also this:
> >>
> >> There are over 400 plugins on the current builds.apache.org - most of
> which
> >> we don't need any more, or are replaced with different plugins on the
> new
> >> system. I expect there may be some plugins we still need to install to
> get
> >> you going again, which is why it is vitally important that you start
> >> testing and migrating your jobs over *now*. You should all have auth.
> >>
> >> Any questions, feel free to email the hadoop-migrations@apache.org
> list if
> >> you are one of the projects listed below. The rest of you, not listed, a
> >> similar email to this one will be posted for you shortly on builds@a.o.
> >>
> >>
> >> full details
> >>
> https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
> >>
> >> Patrick
> >>
> >>
> >>
> >>> Patrick
> >>>
> >>>
> >>>>
> >>>> ---------- Forwarded message ---------
> >>>> Da: Gavin McDonald <gm...@apache.org>
> >>>> Date: Gio 16 Lug 2020, 18:33
> >>>> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> >>>> To: builds <bu...@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 Andor Molnar <an...@apache.org>.

Hi Pat,

I have admin rights in the new system too and probably can work on this on Monday.
What’s “matrix” config? Shouldn’t we just replicate the same jobs on the new instance?

Andor



> On 2020. Jul 17., at 2:51, Patrick Hunt <ph...@apache.org> wrote:
> 
> I updated the job I linked earlier based on what's the latest on the legacy
> jenkins. It ran successfully
> https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
> 
> I didn't replicate every config setting - main gap is the spotbugs
> post-build, which seems to be missing from the new jenkins plugins.
> 
> That's just maven master though. Not sure about the rest. Can we do more of
> a "matrix" config in the new system vs cloning all the time?
> 
> Patrick
> 
> On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt <ph...@apache.org> wrote:
> 
>> 
>> On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt <ph...@apache.org> wrote:
>> 
>>> 
>>> 
>>> On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <eo...@gmail.com>
>>> wrote:
>>> 
>>>> FYI
>>>> 
>>> 
>>> Fun. I do notice it says "Hadoop and related projects have their own
>>> migration path to follow" - any insight on that? We are or are not lumped
>>> in? I would assume we are?
>>> 
>>> This (eventual migration) came up a while back on the Hadoop PMC and I
>>> volunteered to try for us (ZK). I was never able to get it to work, I
>>> provided feedback to infra  but they never got back, as such we have a
>>> project here that's not working with some basic dependencies missing:
>>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/
>>> 
>>> That said, we can try again. Can we verify where ZK is supposed to land?
>>> Perhaps we can try to delete and recreate the POC job I created at that
>>> link to see if we can get it working?
>>> 
>>> 
>> I see another email thread on the list saying that we are part of said
>> "related projects". We are expected to move to
>> http://ci-hadoop.apache.org/ within 4 weeks. Seems nodes are already
>> being removed/migrated from the "H#" pool.
>> 
>> Also this:
>> 
>> There are over 400 plugins on the current builds.apache.org - most of which
>> we don't need any more, or are replaced with different plugins on the new
>> system. I expect there may be some plugins we still need to install to get
>> you going again, which is why it is vitally important that you start
>> testing and migrating your jobs over *now*. You should all have auth.
>> 
>> Any questions, feel free to email the hadoop-migrations@apache.org list if
>> you are one of the projects listed below. The rest of you, not listed, a
>> similar email to this one will be posted for you shortly on builds@a.o.
>> 
>> 
>> full details
>> https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
>> 
>> Patrick
>> 
>> 
>> 
>>> Patrick
>>> 
>>> 
>>>> 
>>>> ---------- Forwarded message ---------
>>>> Da: Gavin McDonald <gm...@apache.org>
>>>> Date: Gio 16 Lug 2020, 18:33
>>>> Subject: [IMPORTANT] - Migration to ci-builds.a.o
>>>> To: builds <bu...@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 Patrick Hunt <ph...@apache.org>.

I updated the job I linked earlier based on what's the latest on the legacy
jenkins. It ran successfully
https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/

I didn't replicate every config setting - main gap is the spotbugs
post-build, which seems to be missing from the new jenkins plugins.

That's just maven master though. Not sure about the rest. Can we do more of
a "matrix" config in the new system vs cloning all the time?

Patrick

On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt <ph...@apache.org> wrote:

>
> On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt <ph...@apache.org> wrote:
>
>>
>>
>> On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <eo...@gmail.com>
>> wrote:
>>
>>> FYI
>>>
>>
>> Fun. I do notice it says "Hadoop and related projects have their own
>> migration path to follow" - any insight on that? We are or are not lumped
>> in? I would assume we are?
>>
>> This (eventual migration) came up a while back on the Hadoop PMC and I
>> volunteered to try for us (ZK). I was never able to get it to work, I
>> provided feedback to infra  but they never got back, as such we have a
>> project here that's not working with some basic dependencies missing:
>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/
>>
>> That said, we can try again. Can we verify where ZK is supposed to land?
>> Perhaps we can try to delete and recreate the POC job I created at that
>> link to see if we can get it working?
>>
>>
> I see another email thread on the list saying that we are part of said
> "related projects". We are expected to move to
> http://ci-hadoop.apache.org/ within 4 weeks. Seems nodes are already
> being removed/migrated from the "H#" pool.
>
> Also this:
>
> There are over 400 plugins on the current builds.apache.org - most of which
> we don't need any more, or are replaced with different plugins on the new
> system. I expect there may be some plugins we still need to install to get
> you going again, which is why it is vitally important that you start
> testing and migrating your jobs over *now*. You should all have auth.
>
> Any questions, feel free to email the hadoop-migrations@apache.org list if
> you are one of the projects listed below. The rest of you, not listed, a
> similar email to this one will be posted for you shortly on builds@a.o.
>
>
> full details
> https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
>
> Patrick
>
>
>
>> Patrick
>>
>>
>>>
>>> ---------- Forwarded message ---------
>>> Da: Gavin McDonald <gm...@apache.org>
>>> Date: Gio 16 Lug 2020, 18:33
>>> Subject: [IMPORTANT] - Migration to ci-builds.a.o
>>> To: builds <bu...@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 Patrick Hunt <ph...@apache.org>.

On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt <ph...@apache.org> wrote:

>
>
> On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <eo...@gmail.com>
> wrote:
>
>> FYI
>>
>
> Fun. I do notice it says "Hadoop and related projects have their own
> migration path to follow" - any insight on that? We are or are not lumped
> in? I would assume we are?
>
> This (eventual migration) came up a while back on the Hadoop PMC and I
> volunteered to try for us (ZK). I was never able to get it to work, I
> provided feedback to infra  but they never got back, as such we have a
> project here that's not working with some basic dependencies missing:
> https://ci-hadoop.apache.org/job/zookeeper-master-maven/
>
> That said, we can try again. Can we verify where ZK is supposed to land?
> Perhaps we can try to delete and recreate the POC job I created at that
> link to see if we can get it working?
>
>
I see another email thread on the list saying that we are part of said
"related projects". We are expected to move to http://ci-hadoop.apache.org/
within 4 weeks. Seems nodes are already being removed/migrated from the
"H#" pool.

Also this:

There are over 400 plugins on the current builds.apache.org - most of which
we don't need any more, or are replaced with different plugins on the new
system. I expect there may be some plugins we still need to install to get
you going again, which is why it is vitally important that you start
testing and migrating your jobs over *now*. You should all have auth.

Any questions, feel free to email the hadoop-migrations@apache.org list if
you are one of the projects listed below. The rest of you, not listed, a
similar email to this one will be posted for you shortly on builds@a.o.


full details
https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E

Patrick



> Patrick
>
>
>>
>> ---------- Forwarded message ---------
>> Da: Gavin McDonald <gm...@apache.org>
>> Date: Gio 16 Lug 2020, 18:33
>> Subject: [IMPORTANT] - Migration to ci-builds.a.o
>> To: builds <bu...@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 Patrick Hunt <ph...@apache.org>.

On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <eo...@gmail.com>
wrote:

> FYI
>

Fun. I do notice it says "Hadoop and related projects have their own
migration path to follow" - any insight on that? We are or are not lumped
in? I would assume we are?

This (eventual migration) came up a while back on the Hadoop PMC and I
volunteered to try for us (ZK). I was never able to get it to work, I
provided feedback to infra  but they never got back, as such we have a
project here that's not working with some basic dependencies missing:
https://ci-hadoop.apache.org/job/zookeeper-master-maven/

That said, we can try again. Can we verify where ZK is supposed to land?
Perhaps we can try to delete and recreate the POC job I created at that
link to see if we can get it working?

Patrick


>
> ---------- Forwarded message ---------
> Da: Gavin McDonald <gm...@apache.org>
> Date: Gio 16 Lug 2020, 18:33
> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> To: builds <bu...@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
>

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

Posted by Enrico Olivelli <eo...@gmail.com>.

FYI

---------- Forwarded message ---------
Da: Gavin McDonald <gm...@apache.org>
Date: Gio 16 Lug 2020, 18:33
Subject: [IMPORTANT] - Migration to ci-builds.a.o
To: builds <bu...@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: Fwd: [IMPORTANT] - Migration to ci-builds.a.o

Posted by Timothy Bish <ta...@gmail.com>.

I've attempted to migrate the old CI jobs that were actually running.  
The SNAPSHOT deploy jobs seemed to have worked and the other test run 
jobs are running with failing tests as before.  I'd recommend folks 
check the projects they are concerned about and see if other jobs are 
needed and / or check the test results of the current jobs to try and 
stabilize the builds.

On 7/24/20 8:32 AM, Robbie Gemmell wrote:
> I haven't seen this mail discussed, or any jobs migrated onto the new
> Jenkins setup, so I thought I'd forward it in case folks aren't
> actually aware.
>
> Existing Jenkins jobs need to be migrated to the new servers or the
> job will effectively be lost on August 15th. You need to ask for an
> ActiveMQ job folder to be created (via Jira, or there is a specific
> mail thread for it now) on the new server first so you can add jobs in
> it.
>
> I added a view to the old Jenkins to group any existing "ActiveMQ.*"
> named jobs, which folks might want to migrate (I think a view like
> this used to exist, but I couldn't see it so I made one):
> https://builds.apache.org/view/A-D/view/ActiveMQ/
>
> More threads and details on builds@a.o
> (https://lists.apache.org/list.html?builds@apache.org)
>
> Robbie
>
> ---------- Forwarded message ---------
> From: Gavin McDonald <gm...@apache.org>
> Date: Thu, 16 Jul 2020 at 17:33
> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> To: builds <bu...@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


-- 
Tim Bish

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

Posted by Timothy Bish <ta...@gmail.com>.

I requested a folder be created for ActiveMQ and they've finally gotten 
round to it
https://ci-builds.apache.org/job/ActiveMQ/

Can now start to migrate jobs to the new CI

On 7/24/20 8:32 AM, Robbie Gemmell wrote:
> I haven't seen this mail discussed, or any jobs migrated onto the new
> Jenkins setup, so I thought I'd forward it in case folks aren't
> actually aware.
>
> Existing Jenkins jobs need to be migrated to the new servers or the
> job will effectively be lost on August 15th. You need to ask for an
> ActiveMQ job folder to be created (via Jira, or there is a specific
> mail thread for it now) on the new server first so you can add jobs in
> it.
>
> I added a view to the old Jenkins to group any existing "ActiveMQ.*"
> named jobs, which folks might want to migrate (I think a view like
> this used to exist, but I couldn't see it so I made one):
> https://builds.apache.org/view/A-D/view/ActiveMQ/
>
> More threads and details on builds@a.o
> (https://lists.apache.org/list.html?builds@apache.org)
>
> Robbie
>
> ---------- Forwarded message ---------
> From: Gavin McDonald <gm...@apache.org>
> Date: Thu, 16 Jul 2020 at 17:33
> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> To: builds <bu...@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


-- 
Tim Bish

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

Posted by Robbie Gemmell <ro...@gmail.com>.

I haven't seen this mail discussed, or any jobs migrated onto the new
Jenkins setup, so I thought I'd forward it in case folks aren't
actually aware.

Existing Jenkins jobs need to be migrated to the new servers or the
job will effectively be lost on August 15th. You need to ask for an
ActiveMQ job folder to be created (via Jira, or there is a specific
mail thread for it now) on the new server first so you can add jobs in
it.

I added a view to the old Jenkins to group any existing "ActiveMQ.*"
named jobs, which folks might want to migrate (I think a view like
this used to exist, but I couldn't see it so I made one):
https://builds.apache.org/view/A-D/view/ActiveMQ/

More threads and details on builds@a.o
(https://lists.apache.org/list.html?builds@apache.org)

Robbie

---------- Forwarded message ---------
From: Gavin McDonald <gm...@apache.org>
Date: Thu, 16 Jul 2020 at 17:33
Subject: [IMPORTANT] - Migration to ci-builds.a.o
To: builds <bu...@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 Paul King <pa...@asert.com.au>.

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 <rl...@apache.org> 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 <zo...@regvart.com>
>
> > On Tue, Jul 21, 2020 at 9:40 PM Eugen Stan <eu...@netdava.com>
> 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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Eric.

On Wed, Jul 22, 2020 at 1:17 PM Eric Barboni <sk...@apache.org> 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 <rl...@apache.org>
> 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 <zo...@regvart.com>
>
> > On Tue, Jul 21, 2020 at 9:40 PM Eugen Stan <eu...@netdava.com>
> 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

Posted by Eric Barboni <sk...@apache.org>.

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 <rl...@apache.org> 
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 <zo...@regvart.com>

> On Tue, Jul 21, 2020 at 9:40 PM Eugen Stan <eu...@netdava.com> 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

Posted by Roy Lenferink <rl...@apache.org>.

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 <zo...@regvart.com>

> On Tue, Jul 21, 2020 at 9:40 PM Eugen Stan <eu...@netdava.com> 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

Posted by Eugen Stan <eu...@netdava.com>.

La 21.07.2020 23:08, Zoran Regvart a scris:
> On Tue, Jul 21, 2020 at 9:40 PM Eugen Stan <eu...@netdava.com> 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

Posted by Zoran Regvart <zo...@regvart.com>.

On Tue, Jul 21, 2020 at 9:40 PM Eugen Stan <eu...@netdava.com> 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

Posted by Eugen Stan <eu...@netdava.com>.

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

Posted by Zoran Regvart <zo...@regvart.com>.

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 <gm...@apache.org> 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

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

Posted by Dave Fisher <wa...@apache.org>.

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 Gavin McDonald <gm...@apache.org>.

Hi Lukasz

On Fri, Jul 17, 2020 at 1:08 PM Lukasz Lenart <lu...@apache.org>
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

Posted by Lukasz Lenart <lu...@apache.org>.

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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Lukasz

On Fri, Jul 17, 2020 at 1:03 PM Lukasz Lenart <lu...@apache.org>
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

Posted by Lukasz Lenart <lu...@apache.org>.

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

Posted by Lukasz Lenart <lu...@apache.org>.

pt., 17 lip 2020 o 11:58 Gavin McDonald <gm...@apache.org> napisał(a):

>
>
> On Fri, Jul 17, 2020 at 7:33 AM Lukasz Lenart <lu...@apache.org>
> wrote:
>
>> pt., 17 lip 2020 o 07:31 Lukasz Lenart <lu...@apache.org>
>> 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

Posted by Gavin McDonald <gm...@apache.org>.

On Fri, Jul 17, 2020 at 7:33 AM Lukasz Lenart <lu...@apache.org>
wrote:

> pt., 17 lip 2020 o 07:31 Lukasz Lenart <lu...@apache.org>
> 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

Posted by Lukasz Lenart <lu...@apache.org>.

pt., 17 lip 2020 o 07:31 Lukasz Lenart <lu...@apache.org> 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

Posted by Lukasz Lenart <lu...@apache.org>.

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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Matt,

On Thu, Jul 16, 2020 at 11:38 PM Matt Sicker <bo...@gmail.com> 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 <bo...@gmail.com> wrote:
> >
> > Oh, I misread the initial email. Could you create a folder for Logging?
> >
> > On Thu, 16 Jul 2020 at 16:31, Matt Sicker <bo...@gmail.com> 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 <gm...@apache.org>
> 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 <bo...@gmail.com>
> >
> >
> >
> > --
> > Matt Sicker <bo...@gmail.com>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
>


-- 

*Gavin McDonald*
Systems Administrator
ASF Infrastructure Team

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

Posted by Gavin McDonald <gm...@apache.org>.

HI Matt

On Thu, Jul 16, 2020 at 11:38 PM Matt Sicker <bo...@gmail.com> 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 <bo...@gmail.com> wrote:
> >
> > Oh, I misread the initial email. Could you create a folder for Logging?
> >
> > On Thu, 16 Jul 2020 at 16:31, Matt Sicker <bo...@gmail.com> 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 <gm...@apache.org>
> 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 <bo...@gmail.com>
> >
> >
> >
> > --
> > Matt Sicker <bo...@gmail.com>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
>


-- 

*Gavin McDonald*
Systems Administrator
ASF Infrastructure Team

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

Posted by Matt Sicker <bo...@gmail.com>.

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 <bo...@gmail.com> wrote:
>
> Oh, I misread the initial email. Could you create a folder for Logging?
>
> On Thu, 16 Jul 2020 at 16:31, Matt Sicker <bo...@gmail.com> 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 <gm...@apache.org> 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 <bo...@gmail.com>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>



-- 
Matt Sicker <bo...@gmail.com>

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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Matt

On Thu, Jul 16, 2020 at 11:33 PM Matt Sicker <bo...@gmail.com> 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 <bo...@gmail.com> 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 <gm...@apache.org>
> 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 <bo...@gmail.com>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
>


-- 

*Gavin McDonald*
Systems Administrator
ASF Infrastructure Team

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

Posted by Matt Sicker <bo...@gmail.com>.

Oh, I misread the initial email. Could you create a folder for Logging?

On Thu, 16 Jul 2020 at 16:31, Matt Sicker <bo...@gmail.com> 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 <gm...@apache.org> 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 <bo...@gmail.com>



-- 
Matt Sicker <bo...@gmail.com>

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

Posted by Matt Sicker <bo...@gmail.com>.

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 <gm...@apache.org> 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 <bo...@gmail.com>

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

Posted by Anup Ghatage <gh...@gmail.com>.

Great chance to review all existing jobs and add new jobs! (Like the slack
digest and other bot jobs)

On Thu, Jul 16, 2020, 12:56 PM Enrico Olivelli <eo...@gmail.com> wrote:

> FYI
>
> ---------- Forwarded message ---------
> Da: Gavin McDonald <gm...@apache.org>
> Date: Gio 16 Lug 2020, 18:33
> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> To: builds <bu...@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
>

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

Posted by Enrico Olivelli <eo...@gmail.com>.

FYI

---------- Forwarded message ---------
Da: Gavin McDonald <gm...@apache.org>
Date: Gio 16 Lug 2020, 18:33
Subject: [IMPORTANT] - Migration to ci-builds.a.o
To: builds <bu...@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 Ismael Juma <is...@juma.me.uk>.

I migrated kafka-trunk and kafka 2.x builds to the new CI server. I have
not migrated kafka 1.x and older since 1.1.0 is nearly 2.5 years old by
now. Does anyone feel strongly that we should migrate 1.x builds?

The PR builds have not been migrated yet as the plugin we depend on is not
installed in the new CI server. Waiting for Apache Infra to either install
it or to tell us that we need an alternative.

Let me know if you have any questions or if you see anything weird.

Ismael

On Tue, Aug 11, 2020 at 12:50 AM Ismael Juma <is...@juma.me.uk> wrote:

> Hi all,
>
> Looks like we have 4 days to migrate all of our Jenkins builds to the new
> CI server. I have started the process:
>
> https://ci-builds.apache.org/job/Kafka/
>
> To avoid confusion, I have disabled the equivalent builds in the old CI
> server. I will migrate a few more tomorrow.
>
> Ismael
>
> ---------- Forwarded message ---------
> From: Gavin McDonald <gm...@apache.org>
> Date: Thu, Jul 16, 2020 at 9:33 AM
> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> To: builds <bu...@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
>

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

Posted by Ismael Juma <is...@juma.me.uk>.

Hi all,

Looks like we have 4 days to migrate all of our Jenkins builds to the new
CI server. I have started the process:

https://ci-builds.apache.org/job/Kafka/

To avoid confusion, I have disabled the equivalent builds in the old CI
server. I will migrate a few more tomorrow.

Ismael

---------- Forwarded message ---------
From: Gavin McDonald <gm...@apache.org>
Date: Thu, Jul 16, 2020 at 9:33 AM
Subject: [IMPORTANT] - Migration to ci-builds.a.o
To: builds <bu...@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 Puja Valiyil <pu...@gmail.com>.

Hey Aaron,
I remember David saying he could work on this a few days ago!


Sent from my iPhone

> On Jul 17, 2020, at 4:03 PM, Adina Crainiceanu <ad...@usna.edu> wrote:
> 
> 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 <gm...@apache.org>
>> 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
> adina@usna.edu
> http://www.usna.edu/Users/cs/adina/

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

Posted by Callum Antonio <ca...@gmail.com>.

All done

On Fri, 17 Jul 2020 at 21:03, Adina Crainiceanu <ad...@usna.edu> wrote:

> 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 <gm...@apache.org>
> 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
> adina@usna.edu
> http://www.usna.edu/Users/cs/adina/
>

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

Posted by Adina Crainiceanu <ad...@usna.edu>.

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 <gm...@apache.org>
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
adina@usna.edu
http://www.usna.edu/Users/cs/adina/

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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Martin,

On Sat, Jul 18, 2020 at 7:14 AM Martin <ma...@apache.org> 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

Posted by Martin <ma...@apache.org>.

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: Fwd: [IMPORTANT] - Migration to ci-builds.a.o

Posted by Andreas Lehmkuehler <an...@lehmi.de>.

I've copied th sonar build as well, but it is incomplete due to a missing 
password for sonar.

@Tilman Do you know the password?

Andreas

Am 19.07.20 um 16:06 schrieb Andreas Lehmkuehler:
> Hi,
> 
> I've recreated all jobs but PDFBox-2.0.x-jdk6 on the new ci server.
> 
> Please have a look if anything important is missing.
> 
> Andreas
> 
> Am 18.07.20 um 12:18 schrieb Andreas Lehmkuehler:
>> Hi,
>>
>> the jenkins master server will be moved to a new home [1], see mail below.
>>
>> I've already asked for a folder for PDFBox [2], folders will replace the Views 
>> from the old installation, see below for details.
>>
>> It is possible to restrict the access the our folder, it is disabled per 
>> default. Do you think it is necessary?
>>
>> I've started the migration with the JBIG2 plugin as the svn integration isn't 
>> available until the next jenkins restart. The new build works so that I've 
>> disabled the old one.
>>
>>
>> Andreas
>>
>> [1] https://ci-builds.apache.org
>> [2] https://ci-builds.apache.org/job/PDFBox/
>>
>> -------- Weitergeleitete Nachricht --------
>> Betreff: [IMPORTANT] - Migration to ci-builds.a.o
>> Datum: Thu, 16 Jul 2020 18:33:08 +0200
>> Von: Gavin McDonald <gm...@apache.org>
>> Antwort an: builds@apache.org, gmcdonald@apache.org
>> An: builds <bu...@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 ...
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
> For additional commands, e-mail: dev-help@pdfbox.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org

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

Posted by Tilman Hausherr <TH...@t-online.de>.

Am 19.07.2020 um 16:06 schrieb Andreas Lehmkuehler:
>
> I've recreated all jobs but PDFBox-2.0.x-jdk6 on the new ci server.
>
> Please have a look if anything important is missing.


Thanks, great job.

I've closed that jdk6 issue. I'll run a build on my machine each time 
before release, just to make sure it still works. I've reverted the 
changes from that issue because they were slowing the build.

Tilman


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org

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

Posted by Andreas Lehmkuehler <an...@lehmi.de>.

Hi,

I've recreated all jobs but PDFBox-2.0.x-jdk6 on the new ci server.

Please have a look if anything important is missing.

Andreas

Am 18.07.20 um 12:18 schrieb Andreas Lehmkuehler:
> Hi,
> 
> the jenkins master server will be moved to a new home [1], see mail below.
> 
> I've already asked for a folder for PDFBox [2], folders will replace the Views 
> from the old installation, see below for details.
> 
> It is possible to restrict the access the our folder, it is disabled per 
> default. Do you think it is necessary?
> 
> I've started the migration with the JBIG2 plugin as the svn integration isn't 
> available until the next jenkins restart. The new build works so that I've 
> disabled the old one.
> 
> 
> Andreas
> 
> [1] https://ci-builds.apache.org
> [2] https://ci-builds.apache.org/job/PDFBox/
> 
> -------- Weitergeleitete Nachricht --------
> Betreff: [IMPORTANT] - Migration to ci-builds.a.o
> Datum: Thu, 16 Jul 2020 18:33:08 +0200
> Von: Gavin McDonald <gm...@apache.org>
> Antwort an: builds@apache.org, gmcdonald@apache.org
> An: builds <bu...@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 ...
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org

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

Posted by Andreas Lehmkuehler <an...@lehmi.de>.

Hi,

the jenkins master server will be moved to a new home [1], see mail below.

I've already asked for a folder for PDFBox [2], folders will replace the Views 
from the old installation, see below for details.

It is possible to restrict the access the our folder, it is disabled per 
default. Do you think it is necessary?

I've started the migration with the JBIG2 plugin as the svn integration isn't 
available until the next jenkins restart. The new build works so that I've 
disabled the old one.


Andreas

[1] https://ci-builds.apache.org
[2] https://ci-builds.apache.org/job/PDFBox/

-------- Weitergeleitete Nachricht --------
Betreff: [IMPORTANT] - Migration to ci-builds.a.o
Datum: Thu, 16 Jul 2020 18:33:08 +0200
Von: Gavin McDonald <gm...@apache.org>
Antwort an: builds@apache.org, gmcdonald@apache.org
An: builds <bu...@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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org

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

Posted by Dave Brondsema <da...@brondsema.net>.

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 : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
              <><

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

Posted by Roy Lenferink <rl...@apache.org>.

Pushing to 'asf-site' and 'asf-staging*' branches will be allowed automatically when running on the
git-websites labeled node.

I also just opened a pull request for site building to put the job configuration in version control
instead of being part of the job: https://github.com/apache/jena-site/pull/17

IMO it's a bit nicer to have the job config in git.

On 2020/07/24 12:13:21, Andy Seaborne <an...@apache.org> wrote: 
> I've forgotten the details of how security for site update.
> 
> Is it that is it runs on  the right node (label "git-websites"), it just 
> works? i.e. no credential files needed?
> 
> ----
> 
> The other builds:
> 
> They have started adding worker nodes and I've started copying jobs 
> over. It seems slower than the main server at the moment and there is a 
> massive build queue but they are all waiting on something so Jena jobs 
> are starting within a few seconds.
> 
> I'm trying to reduce the number of things that are kept (artifacts) and 
> setting the various JDK jobs to poll only hourly.  All this this can be 
> changed, it's just a chance to review setup and play nice.
> 
> Jobs on the old server are still there.
> 
>      Andy
> 
> 
> 
> On 17/07/2020 21:58, Andy Seaborne wrote:
> > Thanks!
> > 
> > Fingers-crossed - copying the job across will work.  It's not like the 
> > site build is unique for Jena.
> > 
> > Good timing WRT the recent release as well.
> > 
> >      Andy
> > 
> > On 17/07/2020 21:31, Roy Lenferink wrote:
> >> If any help is needed with the re-creation of the jena-site job let me 
> >> know
> >> !
> >>
> >> Roy
> >>
> >> Op vr 17 jul. 2020 om 22:21 schreef Andy Seaborne <an...@apache.org>
> >>
> >>> Jenkins is on the move.
> >>>
> >>> I've asked for a Folder on the new system.
> >>>
> >>> I am so glad we have a simple build setup!
> >>>
> >>>       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

Posted by Andy Seaborne <an...@apache.org>.

I've forgotten the details of how security for site update.

Is it that is it runs on  the right node (label "git-websites"), it just 
works? i.e. no credential files needed?

----

The other builds:

They have started adding worker nodes and I've started copying jobs 
over. It seems slower than the main server at the moment and there is a 
massive build queue but they are all waiting on something so Jena jobs 
are starting within a few seconds.

I'm trying to reduce the number of things that are kept (artifacts) and 
setting the various JDK jobs to poll only hourly.  All this this can be 
changed, it's just a chance to review setup and play nice.

Jobs on the old server are still there.

     Andy



On 17/07/2020 21:58, Andy Seaborne wrote:
> Thanks!
> 
> Fingers-crossed - copying the job across will work.  It's not like the 
> site build is unique for Jena.
> 
> Good timing WRT the recent release as well.
> 
>      Andy
> 
> On 17/07/2020 21:31, Roy Lenferink wrote:
>> If any help is needed with the re-creation of the jena-site job let me 
>> know
>> !
>>
>> Roy
>>
>> Op vr 17 jul. 2020 om 22:21 schreef Andy Seaborne <an...@apache.org>
>>
>>> Jenkins is on the move.
>>>
>>> I've asked for a Folder on the new system.
>>>
>>> I am so glad we have a simple build setup!
>>>
>>>       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

Posted by Andy Seaborne <an...@apache.org>.

Thanks!

Fingers-crossed - copying the job across will work.  It's not like the 
site build is unique for Jena.

Good timing WRT the recent release as well.

     Andy

On 17/07/2020 21:31, Roy Lenferink wrote:
> If any help is needed with the re-creation of the jena-site job let me know
> !
> 
> Roy
> 
> Op vr 17 jul. 2020 om 22:21 schreef Andy Seaborne <an...@apache.org>
> 
>> Jenkins is on the move.
>>
>> I've asked for a Folder on the new system.
>>
>> I am so glad we have a simple build setup!
>>
>>       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

Posted by Roy Lenferink <rl...@apache.org>.

If any help is needed with the re-creation of the jena-site job let me know
!

Roy

Op vr 17 jul. 2020 om 22:21 schreef Andy Seaborne <an...@apache.org>

> Jenkins is on the move.
>
> I've asked for a Folder on the new system.
>
> I am so glad we have a simple build setup!
>
>      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 ...
> >
>

Migration to ci-builds.a.o

Posted by Andy Seaborne <an...@apache.org>.

https://ci-builds.apache.org/job/Jena/

On 17/07/2020 21:21, Andy Seaborne wrote:
> Jenkins is on the move.
> 
> I've asked for a Folder on the new system.
> 
> I am so glad we have a simple build setup!
> 
>      Andy

I've created the dev-test job. It has github integration enabled so from 
changes you can click to go to commits. it also builds from the GH repo. 
I simple change to the ASF code repo caused the job to run automatically.

Nothing has been deleted on the old build server but I've disabled 
several jobs to reduce the noise.

Basically, looking good.

More jobs to move across as time permits.
The new Jenkins server is still being configured so it is having more 
restarts than normal, and is currently under provisioned with job executors.

The Jena website job is the important one but again I hope it's a matter 
of check then cut&paste.

(all the other jobs are the same type as the dev-test one with slightly 
different settings).

     Andy

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

Posted by Andy Seaborne <an...@apache.org>.

Jenkins is on the move.

I've asked for a Folder on the new system.

I am so glad we have a simple build setup!

     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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Eric,

On Thu, Jul 30, 2020 at 11:32 AM Eric Barboni <sk...@apache.org> 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 <gm...@apache.org>
> Envoyé : jeudi 16 juillet 2020 18:33
> À : builds <bu...@apache.org>
> 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

Posted by Eric Barboni <sk...@apache.org>.

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 <gm...@apache.org>
Envoyé : jeudi 16 juillet 2020 18:33
À : builds <bu...@apache.org>
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

Posted by Robbie Gemmell <ro...@gmail.com>.

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 <gm...@apache.org> 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

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

Posted by Dave Fisher <wa...@apache.org>.

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 Łukasz Lenart <lu...@gmail.com>.

Thanks a lot!

W dniu sob., 18.07.2020 o 12:03 Gavin McDonald <gm...@apache.org>
napisał(a):

> Hi Andreas
>
> On Sat, Jul 18, 2020 at 11:54 AM Andreas Lehmkuehler <an...@lehmi.de>
> 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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Andreas

On Sat, Jul 18, 2020 at 11:54 AM Andreas Lehmkuehler <an...@lehmi.de>
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

Posted by Andreas Lehmkuehler <an...@lehmi.de>.

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 ...
>

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

Posted by Dave Fisher <wa...@apache.org>.

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 "P. Ottlinger" <po...@apache.org>.

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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Phil,

On Sun, Jul 19, 2020 at 9:32 PM P. Ottlinger <po...@apache.org> 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

Posted by "P. Ottlinger" <po...@apache.org>.

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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Phil,

On Fri, Jul 17, 2020 at 8:21 PM P. Ottlinger <po...@apache.org> 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

Posted by "P. Ottlinger" <po...@apache.org>.

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: Migration to ci-builds.a.o

Posted by Andrea Cosentino <an...@gmail.com>.

Thanks Zoran. I migrated the jdk8/11/14 build too. I'm going ahead with the
other builda

Il gio 23 lug 2020, 21:31 Zoran Regvart <zo...@regvart.com> ha scritto:

> Hi Cameleers,
> I've split this into a separate thread so it doesn't glob with the one
> at builds@.
>
> With help from Andrea the website is now building on the new Jenkins
> infrastructure. I've disable the website build on the
> builds.apache.org.
>
> For multibranch pipeline jobs there is no option to disable the build,
> you have to add `/disable` to the URL of the job, e.g.:
>
>
> https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel.website/disable
>
> and then click on `Retry with POST`.
>
> Other than some of the plugins missing on the ci-builds.apache.org
> this seems to be pretty straightforward. One thing I'm not entirely
> sure on is how github credentials will be done, and I don't want to go
> the route of using personal access tokens. I'll ask about that on
> builds@.
>
> zoran
>
> On Tue, Jul 21, 2020 at 9:29 PM Zoran Regvart <zo...@regvart.com> wrote:
> >
> > FYI
> > we need to start migrating jobs from the current Jenkins at
> > builds.apache.org to the new SaaS offering at ci-builds.apache.org
> >
> > zoran
> >
> > ---------- Forwarded message ---------
> > From: Gavin McDonald <gm...@apache.org>
> > Date: Thu, Jul 16, 2020 at 6:33 PM
> > Subject: [IMPORTANT] - Migration to ci-builds.a.o
> > To: builds <bu...@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
> >
> >
> > --
> > Zoran Regvart
>
>
>
> --
> Zoran Regvart
>

Migration to ci-builds.a.o

Posted by Zoran Regvart <zo...@regvart.com>.

Hi Cameleers,
I've split this into a separate thread so it doesn't glob with the one
at builds@.

With help from Andrea the website is now building on the new Jenkins
infrastructure. I've disable the website build on the
builds.apache.org.

For multibranch pipeline jobs there is no option to disable the build,
you have to add `/disable` to the URL of the job, e.g.:

https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel.website/disable

and then click on `Retry with POST`.

Other than some of the plugins missing on the ci-builds.apache.org
this seems to be pretty straightforward. One thing I'm not entirely
sure on is how github credentials will be done, and I don't want to go
the route of using personal access tokens. I'll ask about that on
builds@.

zoran

On Tue, Jul 21, 2020 at 9:29 PM Zoran Regvart <zo...@regvart.com> wrote:
>
> FYI
> we need to start migrating jobs from the current Jenkins at
> builds.apache.org to the new SaaS offering at ci-builds.apache.org
>
> zoran
>
> ---------- Forwarded message ---------
> From: Gavin McDonald <gm...@apache.org>
> Date: Thu, Jul 16, 2020 at 6:33 PM
> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> To: builds <bu...@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
>
>
> --
> Zoran Regvart



-- 
Zoran Regvart

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

Posted by Andrea Cosentino <an...@yahoo.com.INVALID>.

I'll create an issue to not forget

Inviato da Yahoo Mail su Android 
 
  Il mar, 21 lug, 2020 alle 21:30, Zoran Regvart<zo...@regvart.com> ha scritto:   FYI
we need to start migrating jobs from the current Jenkins at
builds.apache.org to the new SaaS offering at ci-builds.apache.org

zoran

---------- Forwarded message ---------
From: Gavin McDonald <gm...@apache.org>
Date: Thu, Jul 16, 2020 at 6:33 PM
Subject: [IMPORTANT] - Migration to ci-builds.a.o
To: builds <bu...@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


-- 
Zoran Regvart

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

Posted by Zoran Regvart <zo...@regvart.com>.

FYI
we need to start migrating jobs from the current Jenkins at
builds.apache.org to the new SaaS offering at ci-builds.apache.org

zoran

---------- Forwarded message ---------
From: Gavin McDonald <gm...@apache.org>
Date: Thu, Jul 16, 2020 at 6:33 PM
Subject: [IMPORTANT] - Migration to ci-builds.a.o
To: builds <bu...@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

-- 
Zoran Regvart

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

Posted by Adina Crainiceanu <ad...@usna.edu>.

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 <gm...@apache.org>
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
adina@usna.edu
http://www.usna.edu/Users/cs/adina/

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

Posted by Ismael Juma <is...@juma.me.uk>.

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 <is...@juma.me.uk> wrote:

> Hi,
>
> Can you please create a folder for Kafka?
>
> Ismael
>
> On Thu, Jul 16, 2020 at 9:33 AM Gavin McDonald <gm...@apache.org>
> 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

Posted by Ismael Juma <is...@juma.me.uk>.

Hi,

Can you please create a folder for Kafka?

Ismael

On Thu, Jul 16, 2020 at 9:33 AM Gavin McDonald <gm...@apache.org> 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: Changes to the Apache CI build system - volunteer needed

Posted by Richard Downer <ri...@apache.org>.

Hmm! Oh well, I won't argue with Infra :-)

Thanks again for doing this Thomas. Let's let it run for a week or two,
then we can delete the jobs off the old Jenkins instance.

Richard.


On Tue, 21 Jul 2020 at 15:47, Thomas Bouron <th...@cloudsoft.io>
wrote:

> Hi Richard.
>
> When I implemented the jobs on the old build machine, I asked the exact
> same question and INFRA told me to use a personal token as it should be
> bound to a committer on Brooklyn rather than INFRA.
>
> Could ask again but I don't think it has changed.
>
> Best.
>
> On Tue, 21 Jul 2020 at 15:37, Richard Downer <ri...@apache.org> wrote:
>
> > Hi Thomas,
> >
> > That was quick! Thanks for taking care of this.
> >
> > Seems that we should remove the dependency on your own personal access
> > token though. There must be another way to do this. Would you discuss on
> > the builds@apache.org mailing list if there's an alternative method
> which
> > doesn't need any of your own credentials?
> >
> > Richard.
> >
> >
> > On Tue, 21 Jul 2020 at 11:21, Thomas Bouron <th...@cloudsoft.io>
> > wrote:
> >
> > > Hi all.
> > >
> > > I just recreated the job on the new build machine:
> > > https://ci-builds.apache.org/job/Brooklyn/
> > > Like the ones on the old build machine, these jobs are using one of my
> > own
> > > personal token to access GitHub.
> > >
> > > They are currently running and *should* just work as all the build
> > > environments have been pushed to docker.
> > >
> > > If you spot any error, please let me know.
> > >
> > > Best.
> > >
> > > On Mon, 20 Jul 2020 at 21:02, Thomas Bouron <
> thomas.bouron@cloudsoft.io>
> > > wrote:
> > >
> > > > Hey Richard.
> > > >
> > > > I was the one creating the latest Jenkins jobs on the old build
> > machine,
> > > > so it shouldn't take me a too long to recreate them, especially since
> > > it's
> > > > now using docker to build stuff.
> > > >
> > > > I'll look at it tomorrow or maximum this week, then report back here
> > once
> > > > done or if I encounter any issues.
> > > >
> > > > Best.
> > > >
> > > > On Mon, 20 Jul 2020, 15:40 Richard Downer, <ri...@apache.org>
> wrote:
> > > >
> > > >> Hello all,
> > > >>
> > > >> Apache Infra have announced that they are retiring their existing
> > > Jenkins
> > > >> infrastructure in favour of a new one managed by CloudBees. Details
> > > below,
> > > >> but TL;DR every project is responsible for manually setting up their
> > > >> project's jobs on the new Jenkins instance (as an automated
> migration
> > is
> > > >> not possible.)
> > > >>
> > > >> Do any of our committers have availability to do this before the
> > > deadline
> > > >> of 15th August?
> > > >>
> > > >> I've requested that a Brooklyn folder is added. Once this is
> available
> > > >> (within a day I expect) all Brooklyn committers should be able to
> > create
> > > >> and manage jobs in that folder.
> > > >>
> > > >> Richard.
> > > >>
> > > >> ---------- Forwarded message ---------
> > > >> From: Gavin McDonald <gm...@apache.org>
> > > >> Date: Thu, 16 Jul 2020 at 17:33
> > > >> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> > > >> To: builds <bu...@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
> > > >>
> > > >
> > >
> > > --
> > > Thomas Bouron
> > > Lead Software Engineer
> > >
> > > *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
> > >
> > > GitHub: https://github.com/tbouron
> > > Twitter: https://twitter.com/eltibouron
> > >
> >
>
>
> --
> Thomas Bouron
> Lead Software Engineer
>
> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
>
> GitHub: https://github.com/tbouron
> Twitter: https://twitter.com/eltibouron
>

Re: Changes to the Apache CI build system - volunteer needed

Posted by Thomas Bouron <th...@cloudsoft.io>.

Hi Richard.

When I implemented the jobs on the old build machine, I asked the exact
same question and INFRA told me to use a personal token as it should be
bound to a committer on Brooklyn rather than INFRA.

Could ask again but I don't think it has changed.

Best.

On Tue, 21 Jul 2020 at 15:37, Richard Downer <ri...@apache.org> wrote:

> Hi Thomas,
>
> That was quick! Thanks for taking care of this.
>
> Seems that we should remove the dependency on your own personal access
> token though. There must be another way to do this. Would you discuss on
> the builds@apache.org mailing list if there's an alternative method which
> doesn't need any of your own credentials?
>
> Richard.
>
>
> On Tue, 21 Jul 2020 at 11:21, Thomas Bouron <th...@cloudsoft.io>
> wrote:
>
> > Hi all.
> >
> > I just recreated the job on the new build machine:
> > https://ci-builds.apache.org/job/Brooklyn/
> > Like the ones on the old build machine, these jobs are using one of my
> own
> > personal token to access GitHub.
> >
> > They are currently running and *should* just work as all the build
> > environments have been pushed to docker.
> >
> > If you spot any error, please let me know.
> >
> > Best.
> >
> > On Mon, 20 Jul 2020 at 21:02, Thomas Bouron <th...@cloudsoft.io>
> > wrote:
> >
> > > Hey Richard.
> > >
> > > I was the one creating the latest Jenkins jobs on the old build
> machine,
> > > so it shouldn't take me a too long to recreate them, especially since
> > it's
> > > now using docker to build stuff.
> > >
> > > I'll look at it tomorrow or maximum this week, then report back here
> once
> > > done or if I encounter any issues.
> > >
> > > Best.
> > >
> > > On Mon, 20 Jul 2020, 15:40 Richard Downer, <ri...@apache.org> wrote:
> > >
> > >> Hello all,
> > >>
> > >> Apache Infra have announced that they are retiring their existing
> > Jenkins
> > >> infrastructure in favour of a new one managed by CloudBees. Details
> > below,
> > >> but TL;DR every project is responsible for manually setting up their
> > >> project's jobs on the new Jenkins instance (as an automated migration
> is
> > >> not possible.)
> > >>
> > >> Do any of our committers have availability to do this before the
> > deadline
> > >> of 15th August?
> > >>
> > >> I've requested that a Brooklyn folder is added. Once this is available
> > >> (within a day I expect) all Brooklyn committers should be able to
> create
> > >> and manage jobs in that folder.
> > >>
> > >> Richard.
> > >>
> > >> ---------- Forwarded message ---------
> > >> From: Gavin McDonald <gm...@apache.org>
> > >> Date: Thu, 16 Jul 2020 at 17:33
> > >> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> > >> To: builds <bu...@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
> > >>
> > >
> >
> > --
> > Thomas Bouron
> > Lead Software Engineer
> >
> > *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
> >
> > GitHub: https://github.com/tbouron
> > Twitter: https://twitter.com/eltibouron
> >
>


-- 
Thomas Bouron
Lead Software Engineer

*Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud

GitHub: https://github.com/tbouron
Twitter: https://twitter.com/eltibouron

Re: Changes to the Apache CI build system - volunteer needed

Posted by Richard Downer <ri...@apache.org>.

Hi Thomas,

That was quick! Thanks for taking care of this.

Seems that we should remove the dependency on your own personal access
token though. There must be another way to do this. Would you discuss on
the builds@apache.org mailing list if there's an alternative method which
doesn't need any of your own credentials?

Richard.


On Tue, 21 Jul 2020 at 11:21, Thomas Bouron <th...@cloudsoft.io>
wrote:

> Hi all.
>
> I just recreated the job on the new build machine:
> https://ci-builds.apache.org/job/Brooklyn/
> Like the ones on the old build machine, these jobs are using one of my own
> personal token to access GitHub.
>
> They are currently running and *should* just work as all the build
> environments have been pushed to docker.
>
> If you spot any error, please let me know.
>
> Best.
>
> On Mon, 20 Jul 2020 at 21:02, Thomas Bouron <th...@cloudsoft.io>
> wrote:
>
> > Hey Richard.
> >
> > I was the one creating the latest Jenkins jobs on the old build machine,
> > so it shouldn't take me a too long to recreate them, especially since
> it's
> > now using docker to build stuff.
> >
> > I'll look at it tomorrow or maximum this week, then report back here once
> > done or if I encounter any issues.
> >
> > Best.
> >
> > On Mon, 20 Jul 2020, 15:40 Richard Downer, <ri...@apache.org> wrote:
> >
> >> Hello all,
> >>
> >> Apache Infra have announced that they are retiring their existing
> Jenkins
> >> infrastructure in favour of a new one managed by CloudBees. Details
> below,
> >> but TL;DR every project is responsible for manually setting up their
> >> project's jobs on the new Jenkins instance (as an automated migration is
> >> not possible.)
> >>
> >> Do any of our committers have availability to do this before the
> deadline
> >> of 15th August?
> >>
> >> I've requested that a Brooklyn folder is added. Once this is available
> >> (within a day I expect) all Brooklyn committers should be able to create
> >> and manage jobs in that folder.
> >>
> >> Richard.
> >>
> >> ---------- Forwarded message ---------
> >> From: Gavin McDonald <gm...@apache.org>
> >> Date: Thu, 16 Jul 2020 at 17:33
> >> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> >> To: builds <bu...@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
> >>
> >
>
> --
> Thomas Bouron
> Lead Software Engineer
>
> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
>
> GitHub: https://github.com/tbouron
> Twitter: https://twitter.com/eltibouron
>

Re: Changes to the Apache CI build system - volunteer needed

Posted by Thomas Bouron <th...@cloudsoft.io>.

Hi all.

I just recreated the job on the new build machine:
https://ci-builds.apache.org/job/Brooklyn/
Like the ones on the old build machine, these jobs are using one of my own
personal token to access GitHub.

They are currently running and *should* just work as all the build
environments have been pushed to docker.

If you spot any error, please let me know.

Best.

On Mon, 20 Jul 2020 at 21:02, Thomas Bouron <th...@cloudsoft.io>
wrote:

> Hey Richard.
>
> I was the one creating the latest Jenkins jobs on the old build machine,
> so it shouldn't take me a too long to recreate them, especially since it's
> now using docker to build stuff.
>
> I'll look at it tomorrow or maximum this week, then report back here once
> done or if I encounter any issues.
>
> Best.
>
> On Mon, 20 Jul 2020, 15:40 Richard Downer, <ri...@apache.org> wrote:
>
>> Hello all,
>>
>> Apache Infra have announced that they are retiring their existing Jenkins
>> infrastructure in favour of a new one managed by CloudBees. Details below,
>> but TL;DR every project is responsible for manually setting up their
>> project's jobs on the new Jenkins instance (as an automated migration is
>> not possible.)
>>
>> Do any of our committers have availability to do this before the deadline
>> of 15th August?
>>
>> I've requested that a Brooklyn folder is added. Once this is available
>> (within a day I expect) all Brooklyn committers should be able to create
>> and manage jobs in that folder.
>>
>> Richard.
>>
>> ---------- Forwarded message ---------
>> From: Gavin McDonald <gm...@apache.org>
>> Date: Thu, 16 Jul 2020 at 17:33
>> Subject: [IMPORTANT] - Migration to ci-builds.a.o
>> To: builds <bu...@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
>>
>

-- 
Thomas Bouron
Lead Software Engineer

*Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud

GitHub: https://github.com/tbouron
Twitter: https://twitter.com/eltibouron

Re: Changes to the Apache CI build system - volunteer needed

Posted by Thomas Bouron <th...@cloudsoft.io>.

Hey Richard.

I was the one creating the latest Jenkins jobs on the old build machine, so
it shouldn't take me a too long to recreate them, especially since it's now
using docker to build stuff.

I'll look at it tomorrow or maximum this week, then report back here once
done or if I encounter any issues.

Best.

On Mon, 20 Jul 2020, 15:40 Richard Downer, <ri...@apache.org> wrote:

> Hello all,
>
> Apache Infra have announced that they are retiring their existing Jenkins
> infrastructure in favour of a new one managed by CloudBees. Details below,
> but TL;DR every project is responsible for manually setting up their
> project's jobs on the new Jenkins instance (as an automated migration is
> not possible.)
>
> Do any of our committers have availability to do this before the deadline
> of 15th August?
>
> I've requested that a Brooklyn folder is added. Once this is available
> (within a day I expect) all Brooklyn committers should be able to create
> and manage jobs in that folder.
>
> Richard.
>
> ---------- Forwarded message ---------
> From: Gavin McDonald <gm...@apache.org>
> Date: Thu, 16 Jul 2020 at 17:33
> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> To: builds <bu...@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
>

Changes to the Apache CI build system - volunteer needed

Posted by Richard Downer <ri...@apache.org>.

Hello all,

Apache Infra have announced that they are retiring their existing Jenkins
infrastructure in favour of a new one managed by CloudBees. Details below,
but TL;DR every project is responsible for manually setting up their
project's jobs on the new Jenkins instance (as an automated migration is
not possible.)

Do any of our committers have availability to do this before the deadline
of 15th August?

I've requested that a Brooklyn folder is added. Once this is available
(within a day I expect) all Brooklyn committers should be able to create
and manage jobs in that folder.

Richard.

---------- Forwarded message ---------
From: Gavin McDonald <gm...@apache.org>
Date: Thu, 16 Jul 2020 at 17:33
Subject: [IMPORTANT] - Migration to ci-builds.a.o
To: builds <bu...@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 Gavin McDonald <gm...@apache.org>.

Hi Vladimir

On Fri, Jul 17, 2020 at 12:48 PM Vladimir Sitnikov <
sitnikov.vladimir@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

Posted by Vladimir Sitnikov <si...@gmail.com>.

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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Sebb

On Thu, Jul 16, 2020 at 11:25 PM sebb <se...@gmail.com> 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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Uwe

On Fri, Jul 17, 2020 at 10:08 AM Uwe Schindler <us...@apache.org>
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
> uschindler@apache.org
> ASF Member, Apache Lucene PMC / Committer
> Bremen, Germany
> https://lucene.apache.org/
>
> > -----Original Message-----
> > From: sebb <se...@gmail.com>
> > Sent: Thursday, July 16, 2020 11:26 PM
> > To: builds <bu...@apache.org>; Gav <gm...@apache.org>
> > Subject: Re: [IMPORTANT] - Migration to ci-builds.a.o
> >
> > On Thu, 16 Jul 2020 at 17:33, Gavin McDonald <gm...@apache.org>
> > 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

Posted by Uwe Schindler <us...@apache.org>.

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
uschindler@apache.org 
ASF Member, Apache Lucene PMC / Committer
Bremen, Germany
https://lucene.apache.org/

> -----Original Message-----
> From: sebb <se...@gmail.com>
> Sent: Thursday, July 16, 2020 11:26 PM
> To: builds <bu...@apache.org>; Gav <gm...@apache.org>
> Subject: Re: [IMPORTANT] - Migration to ci-builds.a.o
> 
> On Thu, 16 Jul 2020 at 17:33, Gavin McDonald <gm...@apache.org>
> 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

Posted by Oleg Kalnichevski <ol...@apache.org>.

On Sun, 2020-07-19 at 11:34 +0200, Michael Osipov wrote:
> Am 2020-07-18 um 16:34 schrieb Oleg Kalnichevski:
> > On Fri, 2020-07-17 at 20:35 +0200, Gavin McDonald wrote:
> > > Hi Oleg
> > > 
> > > On Fri, Jul 17, 2020 at 1:41 PM Oleg Kalnichevski <
> > > oleg@ok2consulting.com> wrote:
> > > > Hi Gavin
> > > > 
> > > > Could you please kindly create a folder for Apache
> > > > HttpComponents?
> > > 
> > > Done
> > >   
> > > > Cheers
> > > > 
> > > > Oleg
> > > > 
> > > 
> > > 
> > 
> > Folks
> > 
> > I moved all our Jenkins jobs to ci-builds.a.o
> 
> 
> Wow, when did ci-builds.a.o happen? This seems to be Jenkins too, is 
> there any difference for us?
> 

It was announced on builds@apache.org. I suppose it should not be much
different as far as we are concerned. Hopefully more stable.

Cheers

Oleg



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org

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

Posted by Michael Osipov <mi...@apache.org>.

Am 2020-07-18 um 16:34 schrieb Oleg Kalnichevski:
> On Fri, 2020-07-17 at 20:35 +0200, Gavin McDonald wrote:
>> Hi Oleg
>>
>> On Fri, Jul 17, 2020 at 1:41 PM Oleg Kalnichevski <
>> oleg@ok2consulting.com> wrote:
>>> Hi Gavin
>>>
>>> Could you please kindly create a folder for Apache HttpComponents?
>>
>> Done
>>   
>>> Cheers
>>>
>>> Oleg
>>>
>>
>>
> 
> Folks
> 
> I moved all our Jenkins jobs to ci-builds.a.o


Wow, when did ci-builds.a.o happen? This seems to be Jenkins too, is 
there any difference for us?


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org

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

Posted by Oleg Kalnichevski <ol...@apache.org>.

On Fri, 2020-07-17 at 20:35 +0200, Gavin McDonald wrote:
> Hi Oleg
> 
> On Fri, Jul 17, 2020 at 1:41 PM Oleg Kalnichevski <
> oleg@ok2consulting.com> wrote:
> > Hi Gavin
> > 
> > Could you please kindly create a folder for Apache HttpComponents?
> 
> Done
>  
> > Cheers
> > 
> > Oleg
> > 
> 
> 

Folks

I moved all our Jenkins jobs to ci-builds.a.o

Cheers

Oleg


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org

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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Oleg

On Fri, Jul 17, 2020 at 1:41 PM Oleg Kalnichevski <ol...@ok2consulting.com>
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

Posted by Gavin McDonald <gm...@apache.org>.

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 <so...@gmail.com>
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 <gm...@apache.org> wrote:
>
>> Hi Maxim,
>>
>> On Sat, Jul 18, 2020 at 3:24 AM Maxim Solodovnik <so...@gmail.com>
>> 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

Posted by Maxim Solodovnik <so...@gmail.com>.

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 <gm...@apache.org> wrote:

> Hi Maxim,
>
> On Sat, Jul 18, 2020 at 3:24 AM Maxim Solodovnik <so...@gmail.com>
> 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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Maxim,

On Sat, Jul 18, 2020 at 3:24 AM Maxim Solodovnik <so...@gmail.com>
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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Maxim

On Sat, Jul 18, 2020 at 3:55 AM Maxim Solodovnik <so...@gmail.com>
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 <gm...@apache.org>
>>> >>> wrote:
>>> >>> >
>>> >>> > Hi Matt
>>> >>> >
>>> >>> > On Sat, Jul 18, 2020 at 12:35 AM Matt Sicker <bo...@gmail.com>
>>> 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 <
>>> gmcdonald@apache.org>
>>> >>> wrote:
>>> >>> >> >
>>> >>> >> > Hi Sebb
>>> >>> >> >
>>> >>> >> > On Fri, Jul 17, 2020 at 11:27 PM sebb <se...@gmail.com> 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 <
>>> >>> gmcdonald@apache.org> wrote:
>>> >>> >> > >
>>> >>> >> > >> Hi Sebb,
>>> >>> >> > >>
>>> >>> >> > >> On Fri, Jul 17, 2020 at 11:04 PM sebb <se...@gmail.com>
>>> wrote:
>>> >>> >> > >>
>>> >>> >> > >>>
>>> >>> >> > >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald <
>>> >>> gmcdonald@apache.org>
>>> >>> >> > >>> wrote:
>>> >>> >> > >>>
>>> >>> >> > >>>> Hi Sebb
>>> >>> >> > >>>>
>>> >>> >> > >>>> On Fri, Jul 17, 2020 at 2:10 PM sebb <se...@gmail.com>
>>> 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 <bo...@gmail.com>
>>> >>> >
>>> >>> >
>>> >>> >
>>> >>> > --
>>> >>> > Gavin McDonald
>>> >>> > Systems Administrator
>>> >>> > ASF Infrastructure Team
>>> >>> >
>>> >>>
>>> >>>
>>> >>> --
>>> >>> Matt Sicker <bo...@gmail.com>
>>> >>>
>>> >>
>>> >>
>>> >> --
>>> >> *Gavin McDonald*
>>> >> Systems Administrator
>>> >> ASF Infrastructure Team
>>> >>
>>> >>
>>> >
>>> > --
>>> > Matt Sicker <bo...@gmail.com>
>>> >
>>>
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>>
>>
>>
>> --
>> Best regards,
>> Maxim
>>
>
>
> --
> Best regards,
> Maxim
>


-- 
*Gavin McDonald*
Systems Administrator
ASF Infrastructure Team

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

Posted by Maxim Solodovnik <so...@gmail.com>.

PR builds also seems to be not enabled

On Sat, 18 Jul 2020 at 08:24, Maxim Solodovnik <so...@gmail.com> 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 <bo...@gmail.com> 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 <bo...@gmail.com> 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 <gm...@apache.org>
>> wrote:
>> >
>> >> Hi Matt
>> >>
>> >> On Sat, Jul 18, 2020 at 12:56 AM Matt Sicker <bo...@gmail.com> 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 <gm...@apache.org>
>> >>> wrote:
>> >>> >
>> >>> > Hi Matt
>> >>> >
>> >>> > On Sat, Jul 18, 2020 at 12:35 AM Matt Sicker <bo...@gmail.com>
>> 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 <gmcdonald@apache.org
>> >
>> >>> wrote:
>> >>> >> >
>> >>> >> > Hi Sebb
>> >>> >> >
>> >>> >> > On Fri, Jul 17, 2020 at 11:27 PM sebb <se...@gmail.com> 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 <
>> >>> gmcdonald@apache.org> wrote:
>> >>> >> > >
>> >>> >> > >> Hi Sebb,
>> >>> >> > >>
>> >>> >> > >> On Fri, Jul 17, 2020 at 11:04 PM sebb <se...@gmail.com>
>> wrote:
>> >>> >> > >>
>> >>> >> > >>>
>> >>> >> > >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald <
>> >>> gmcdonald@apache.org>
>> >>> >> > >>> wrote:
>> >>> >> > >>>
>> >>> >> > >>>> Hi Sebb
>> >>> >> > >>>>
>> >>> >> > >>>> On Fri, Jul 17, 2020 at 2:10 PM sebb <se...@gmail.com>
>> 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 <bo...@gmail.com>
>> >>> >
>> >>> >
>> >>> >
>> >>> > --
>> >>> > Gavin McDonald
>> >>> > Systems Administrator
>> >>> > ASF Infrastructure Team
>> >>> >
>> >>>
>> >>>
>> >>> --
>> >>> Matt Sicker <bo...@gmail.com>
>> >>>
>> >>
>> >>
>> >> --
>> >> *Gavin McDonald*
>> >> Systems Administrator
>> >> ASF Infrastructure Team
>> >>
>> >>
>> >
>> > --
>> > Matt Sicker <bo...@gmail.com>
>> >
>>
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
>
>
> --
> Best regards,
> Maxim
>


-- 
Best regards,
Maxim

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

Posted by Maxim Solodovnik <so...@gmail.com>.

Hello Gavin,

It seems sonar integration is missing (Credentials dropdown for sonar is
missing)

On Sat, 18 Jul 2020 at 06:57, Matt Sicker <bo...@gmail.com> 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 <bo...@gmail.com> 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 <gm...@apache.org>
> wrote:
> >
> >> Hi Matt
> >>
> >> On Sat, Jul 18, 2020 at 12:56 AM Matt Sicker <bo...@gmail.com> 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 <gm...@apache.org>
> >>> wrote:
> >>> >
> >>> > Hi Matt
> >>> >
> >>> > On Sat, Jul 18, 2020 at 12:35 AM Matt Sicker <bo...@gmail.com>
> 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 <gm...@apache.org>
> >>> wrote:
> >>> >> >
> >>> >> > Hi Sebb
> >>> >> >
> >>> >> > On Fri, Jul 17, 2020 at 11:27 PM sebb <se...@gmail.com> 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 <
> >>> gmcdonald@apache.org> wrote:
> >>> >> > >
> >>> >> > >> Hi Sebb,
> >>> >> > >>
> >>> >> > >> On Fri, Jul 17, 2020 at 11:04 PM sebb <se...@gmail.com>
> wrote:
> >>> >> > >>
> >>> >> > >>>
> >>> >> > >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald <
> >>> gmcdonald@apache.org>
> >>> >> > >>> wrote:
> >>> >> > >>>
> >>> >> > >>>> Hi Sebb
> >>> >> > >>>>
> >>> >> > >>>> On Fri, Jul 17, 2020 at 2:10 PM sebb <se...@gmail.com>
> 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 <bo...@gmail.com>
> >>> >
> >>> >
> >>> >
> >>> > --
> >>> > Gavin McDonald
> >>> > Systems Administrator
> >>> > ASF Infrastructure Team
> >>> >
> >>>
> >>>
> >>> --
> >>> Matt Sicker <bo...@gmail.com>
> >>>
> >>
> >>
> >> --
> >> *Gavin McDonald*
> >> Systems Administrator
> >> ASF Infrastructure Team
> >>
> >>
> >
> > --
> > Matt Sicker <bo...@gmail.com>
> >
>
>
> --
> Matt Sicker <bo...@gmail.com>
>


-- 
Best regards,
Maxim

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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Olivier,

On Sat, Jul 18, 2020 at 7:59 AM Olivier Lamy <ol...@apache.org> 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 <bo...@gmail.com> 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 <bo...@gmail.com> 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 <gm...@apache.org>
> > wrote:
> > >
> > >> Hi Matt
> > >>
> > >> On Sat, Jul 18, 2020 at 12:56 AM Matt Sicker <bo...@gmail.com>
> 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 <gm...@apache.org>
> > >>> wrote:
> > >>> >
> > >>> > Hi Matt
> > >>> >
> > >>> > On Sat, Jul 18, 2020 at 12:35 AM Matt Sicker <bo...@gmail.com>
> > 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 <
> gmcdonald@apache.org>
> > >>> wrote:
> > >>> >> >
> > >>> >> > Hi Sebb
> > >>> >> >
> > >>> >> > On Fri, Jul 17, 2020 at 11:27 PM sebb <se...@gmail.com> 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 <
> > >>> gmcdonald@apache.org> wrote:
> > >>> >> > >
> > >>> >> > >> Hi Sebb,
> > >>> >> > >>
> > >>> >> > >> On Fri, Jul 17, 2020 at 11:04 PM sebb <se...@gmail.com>
> > wrote:
> > >>> >> > >>
> > >>> >> > >>>
> > >>> >> > >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald <
> > >>> gmcdonald@apache.org>
> > >>> >> > >>> wrote:
> > >>> >> > >>>
> > >>> >> > >>>> Hi Sebb
> > >>> >> > >>>>
> > >>> >> > >>>> On Fri, Jul 17, 2020 at 2:10 PM sebb <se...@gmail.com>
> > 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 <bo...@gmail.com>
> > >>> >
> > >>> >
> > >>> >
> > >>> > --
> > >>> > Gavin McDonald
> > >>> > Systems Administrator
> > >>> > ASF Infrastructure Team
> > >>> >
> > >>>
> > >>>
> > >>> --
> > >>> Matt Sicker <bo...@gmail.com>
> > >>>
> > >>
> > >>
> > >> --
> > >> *Gavin McDonald*
> > >> Systems Administrator
> > >> ASF Infrastructure Team
> > >>
> > >>
> > >
> > > --
> > > Matt Sicker <bo...@gmail.com>
> > >
> >
> >
> > --
> > Matt Sicker <bo...@gmail.com>
> >
>
>
> --
> 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

Posted by Olivier Lamy <ol...@apache.org>.

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 <bo...@gmail.com> 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 <bo...@gmail.com> 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 <gm...@apache.org>
> wrote:
> >
> >> Hi Matt
> >>
> >> On Sat, Jul 18, 2020 at 12:56 AM Matt Sicker <bo...@gmail.com> 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 <gm...@apache.org>
> >>> wrote:
> >>> >
> >>> > Hi Matt
> >>> >
> >>> > On Sat, Jul 18, 2020 at 12:35 AM Matt Sicker <bo...@gmail.com>
> 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 <gm...@apache.org>
> >>> wrote:
> >>> >> >
> >>> >> > Hi Sebb
> >>> >> >
> >>> >> > On Fri, Jul 17, 2020 at 11:27 PM sebb <se...@gmail.com> 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 <
> >>> gmcdonald@apache.org> wrote:
> >>> >> > >
> >>> >> > >> Hi Sebb,
> >>> >> > >>
> >>> >> > >> On Fri, Jul 17, 2020 at 11:04 PM sebb <se...@gmail.com>
> wrote:
> >>> >> > >>
> >>> >> > >>>
> >>> >> > >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald <
> >>> gmcdonald@apache.org>
> >>> >> > >>> wrote:
> >>> >> > >>>
> >>> >> > >>>> Hi Sebb
> >>> >> > >>>>
> >>> >> > >>>> On Fri, Jul 17, 2020 at 2:10 PM sebb <se...@gmail.com>
> 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 <bo...@gmail.com>
> >>> >
> >>> >
> >>> >
> >>> > --
> >>> > Gavin McDonald
> >>> > Systems Administrator
> >>> > ASF Infrastructure Team
> >>> >
> >>>
> >>>
> >>> --
> >>> Matt Sicker <bo...@gmail.com>
> >>>
> >>
> >>
> >> --
> >> *Gavin McDonald*
> >> Systems Administrator
> >> ASF Infrastructure Team
> >>
> >>
> >
> > --
> > Matt Sicker <bo...@gmail.com>
> >
>
>
> --
> Matt Sicker <bo...@gmail.com>
>


-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Posted by Matt Sicker <bo...@gmail.com>.

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 <gm...@apache.org> wrote:

> Hi Matt
>
> On Sat, Jul 18, 2020 at 1:57 AM Matt Sicker <bo...@gmail.com> 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 <bo...@gmail.com>

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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Matt

On Sat, Jul 18, 2020 at 1:57 AM Matt Sicker <bo...@gmail.com> 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

Posted by Matt Sicker <bo...@gmail.com>.

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 <bo...@gmail.com> 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 <gm...@apache.org> wrote:
>
>> Hi Matt
>>
>> On Sat, Jul 18, 2020 at 12:56 AM Matt Sicker <bo...@gmail.com> 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 <gm...@apache.org>
>>> wrote:
>>> >
>>> > Hi Matt
>>> >
>>> > On Sat, Jul 18, 2020 at 12:35 AM Matt Sicker <bo...@gmail.com> 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 <gm...@apache.org>
>>> wrote:
>>> >> >
>>> >> > Hi Sebb
>>> >> >
>>> >> > On Fri, Jul 17, 2020 at 11:27 PM sebb <se...@gmail.com> 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 <
>>> gmcdonald@apache.org> wrote:
>>> >> > >
>>> >> > >> Hi Sebb,
>>> >> > >>
>>> >> > >> On Fri, Jul 17, 2020 at 11:04 PM sebb <se...@gmail.com> wrote:
>>> >> > >>
>>> >> > >>>
>>> >> > >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald <
>>> gmcdonald@apache.org>
>>> >> > >>> wrote:
>>> >> > >>>
>>> >> > >>>> Hi Sebb
>>> >> > >>>>
>>> >> > >>>> On Fri, Jul 17, 2020 at 2:10 PM sebb <se...@gmail.com> 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 <bo...@gmail.com>
>>> >
>>> >
>>> >
>>> > --
>>> > Gavin McDonald
>>> > Systems Administrator
>>> > ASF Infrastructure Team
>>> >
>>>
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>>
>>
>>
>> --
>> *Gavin McDonald*
>> Systems Administrator
>> ASF Infrastructure Team
>>
>>
>
> --
> Matt Sicker <bo...@gmail.com>
>


-- 
Matt Sicker <bo...@gmail.com>

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

Posted by Matt Sicker <bo...@gmail.com>.

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 <gm...@apache.org> wrote:

> Hi Matt
>
> On Sat, Jul 18, 2020 at 12:56 AM Matt Sicker <bo...@gmail.com> 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 <gm...@apache.org>
>> wrote:
>> >
>> > Hi Matt
>> >
>> > On Sat, Jul 18, 2020 at 12:35 AM Matt Sicker <bo...@gmail.com> 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 <gm...@apache.org>
>> wrote:
>> >> >
>> >> > Hi Sebb
>> >> >
>> >> > On Fri, Jul 17, 2020 at 11:27 PM sebb <se...@gmail.com> 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 <gm...@apache.org>
>> wrote:
>> >> > >
>> >> > >> Hi Sebb,
>> >> > >>
>> >> > >> On Fri, Jul 17, 2020 at 11:04 PM sebb <se...@gmail.com> wrote:
>> >> > >>
>> >> > >>>
>> >> > >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald <
>> gmcdonald@apache.org>
>> >> > >>> wrote:
>> >> > >>>
>> >> > >>>> Hi Sebb
>> >> > >>>>
>> >> > >>>> On Fri, Jul 17, 2020 at 2:10 PM sebb <se...@gmail.com> 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 <bo...@gmail.com>
>> >
>> >
>> >
>> > --
>> > Gavin McDonald
>> > Systems Administrator
>> > ASF Infrastructure Team
>> >
>>
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
>
>
> --
> *Gavin McDonald*
> Systems Administrator
> ASF Infrastructure Team
>
>

-- 
Matt Sicker <bo...@gmail.com>

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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Matt

On Sat, Jul 18, 2020 at 12:56 AM Matt Sicker <bo...@gmail.com> 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 <gm...@apache.org> wrote:
> >
> > Hi Matt
> >
> > On Sat, Jul 18, 2020 at 12:35 AM Matt Sicker <bo...@gmail.com> 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 <gm...@apache.org>
> wrote:
> >> >
> >> > Hi Sebb
> >> >
> >> > On Fri, Jul 17, 2020 at 11:27 PM sebb <se...@gmail.com> 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 <gm...@apache.org>
> wrote:
> >> > >
> >> > >> Hi Sebb,
> >> > >>
> >> > >> On Fri, Jul 17, 2020 at 11:04 PM sebb <se...@gmail.com> wrote:
> >> > >>
> >> > >>>
> >> > >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald <
> gmcdonald@apache.org>
> >> > >>> wrote:
> >> > >>>
> >> > >>>> Hi Sebb
> >> > >>>>
> >> > >>>> On Fri, Jul 17, 2020 at 2:10 PM sebb <se...@gmail.com> 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 <bo...@gmail.com>
> >
> >
> >
> > --
> > Gavin McDonald
> > Systems Administrator
> > ASF Infrastructure Team
> >
>
>
> --
> Matt Sicker <bo...@gmail.com>
>


-- 
*Gavin McDonald*
Systems Administrator
ASF Infrastructure Team

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

Posted by Matt Sicker <bo...@gmail.com>.

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 <gm...@apache.org> wrote:
>
> Hi Matt
>
> On Sat, Jul 18, 2020 at 12:35 AM Matt Sicker <bo...@gmail.com> 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 <gm...@apache.org> wrote:
>> >
>> > Hi Sebb
>> >
>> > On Fri, Jul 17, 2020 at 11:27 PM sebb <se...@gmail.com> 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 <gm...@apache.org> wrote:
>> > >
>> > >> Hi Sebb,
>> > >>
>> > >> On Fri, Jul 17, 2020 at 11:04 PM sebb <se...@gmail.com> wrote:
>> > >>
>> > >>>
>> > >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald <gm...@apache.org>
>> > >>> wrote:
>> > >>>
>> > >>>> Hi Sebb
>> > >>>>
>> > >>>> On Fri, Jul 17, 2020 at 2:10 PM sebb <se...@gmail.com> 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 <bo...@gmail.com>
>
>
>
> --
> Gavin McDonald
> Systems Administrator
> ASF Infrastructure Team
>


-- 
Matt Sicker <bo...@gmail.com>

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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Matt

On Sat, Jul 18, 2020 at 12:35 AM Matt Sicker <bo...@gmail.com> 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 <gm...@apache.org> wrote:
> >
> > Hi Sebb
> >
> > On Fri, Jul 17, 2020 at 11:27 PM sebb <se...@gmail.com> 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 <gm...@apache.org>
> wrote:
> > >
> > >> Hi Sebb,
> > >>
> > >> On Fri, Jul 17, 2020 at 11:04 PM sebb <se...@gmail.com> wrote:
> > >>
> > >>>
> > >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald <gm...@apache.org>
> > >>> wrote:
> > >>>
> > >>>> Hi Sebb
> > >>>>
> > >>>> On Fri, Jul 17, 2020 at 2:10 PM sebb <se...@gmail.com> 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 <bo...@gmail.com>
>


-- 
*Gavin McDonald*
Systems Administrator
ASF Infrastructure Team

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

Posted by Matt Sicker <bo...@gmail.com>.

Could you add the Slack plugin? https://plugins.jenkins.io/slack/

On Fri, 17 Jul 2020 at 17:27, Gavin McDonald <gm...@apache.org> wrote:
>
> Hi Sebb
>
> On Fri, Jul 17, 2020 at 11:27 PM sebb <se...@gmail.com> 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 <gm...@apache.org> wrote:
> >
> >> Hi Sebb,
> >>
> >> On Fri, Jul 17, 2020 at 11:04 PM sebb <se...@gmail.com> wrote:
> >>
> >>>
> >>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald <gm...@apache.org>
> >>> wrote:
> >>>
> >>>> Hi Sebb
> >>>>
> >>>> On Fri, Jul 17, 2020 at 2:10 PM sebb <se...@gmail.com> 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 <bo...@gmail.com>

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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Sebb

On Fri, Jul 17, 2020 at 11:27 PM sebb <se...@gmail.com> 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 <gm...@apache.org> wrote:
>
>> Hi Sebb,
>>
>> On Fri, Jul 17, 2020 at 11:04 PM sebb <se...@gmail.com> wrote:
>>
>>>
>>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald <gm...@apache.org>
>>> wrote:
>>>
>>>> Hi Sebb
>>>>
>>>> On Fri, Jul 17, 2020 at 2:10 PM sebb <se...@gmail.com> 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

Posted by sebb <se...@gmail.com>.

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 <gm...@apache.org> wrote:

> Hi Sebb,
>
> On Fri, Jul 17, 2020 at 11:04 PM sebb <se...@gmail.com> wrote:
>
>>
>> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald <gm...@apache.org>
>> wrote:
>>
>>> Hi Sebb
>>>
>>> On Fri, Jul 17, 2020 at 2:10 PM sebb <se...@gmail.com> 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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Sebb,

On Fri, Jul 17, 2020 at 11:04 PM sebb <se...@gmail.com> wrote:

>
> On Fri, 17 Jul 2020 at 19:49, Gavin McDonald <gm...@apache.org> wrote:
>
>> Hi Sebb
>>
>> On Fri, Jul 17, 2020 at 2:10 PM sebb <se...@gmail.com> 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

Posted by sebb <se...@gmail.com>.

On Fri, 17 Jul 2020 at 19:49, Gavin McDonald <gm...@apache.org> wrote:

> Hi Sebb
>
> On Fri, Jul 17, 2020 at 2:10 PM sebb <se...@gmail.com> 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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Sebb

On Fri, Jul 17, 2020 at 2:10 PM sebb <se...@gmail.com> wrote:

> Please create Commons
>

Added ,please test.

-- 

*Gavin McDonald*
Systems Administrator
ASF Infrastructure Team

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

Posted by Gavin McDonald <gm...@apache.org>.

Hi Eric

On Fri, Jul 17, 2020 at 3:02 PM Eric Barboni <sk...@apache.org> wrote:

> Hi,
>  Would it be possible to create NetBeans folder. Access to commiters.
>

All done, thank you.


>
> Regards
> Eric
>
> -----Message d'origine-----
> De : sebb <se...@gmail.com>
> Envoyé : vendredi 17 juillet 2020 14:11
> À : builds <bu...@apache.org>
> Cc : Gav <gm...@apache.org>
> Objet : Re: [IMPORTANT] - Migration to ci-builds.a.o
>
> Please create Commons
>
> On Fri, 17 Jul 2020 at 12:41, Oleg Kalnichevski <ol...@ok2consulting.com>
> wrote:
> >
> > On Thu, 2020-07-16 at 22:25 +0100, sebb wrote:
> > > On Thu, 16 Jul 2020 at 17:33, Gavin McDonald <gm...@apache.org>
> > > 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

Posted by Eric Barboni <sk...@apache.org>.

Hi, 
 Would it be possible to create NetBeans folder. Access to commiters.

Regards
Eric

-----Message d'origine-----
De : sebb <se...@gmail.com> 
Envoyé : vendredi 17 juillet 2020 14:11
À : builds <bu...@apache.org>
Cc : Gav <gm...@apache.org>
Objet : Re: [IMPORTANT] - Migration to ci-builds.a.o

Please create Commons

On Fri, 17 Jul 2020 at 12:41, Oleg Kalnichevski <ol...@ok2consulting.com> wrote:
>
> On Thu, 2020-07-16 at 22:25 +0100, sebb wrote:
> > On Thu, 16 Jul 2020 at 17:33, Gavin McDonald <gm...@apache.org>
> > 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

Posted by sebb <se...@gmail.com>.

Please create Commons

On Fri, 17 Jul 2020 at 12:41, Oleg Kalnichevski <ol...@ok2consulting.com> wrote:
>
> On Thu, 2020-07-16 at 22:25 +0100, sebb wrote:
> > On Thu, 16 Jul 2020 at 17:33, Gavin McDonald <gm...@apache.org>
> > 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

Posted by Oleg Kalnichevski <ol...@ok2consulting.com>.

On Thu, 2020-07-16 at 22:25 +0100, sebb wrote:
> On Thu, 16 Jul 2020 at 17:33, Gavin McDonald <gm...@apache.org>
> 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

Posted by sebb <se...@gmail.com>.

On Thu, 16 Jul 2020 at 17:33, Gavin McDonald <gm...@apache.org> 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

Posted by Gézapeti Cseh <ge...@apache.org>.

Status report:
After asking for permissions to all PMC members in INFRA-20705
<https://issues.apache.org/jira/browse/INFRA-20705> I've created the new job
<https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/>.
The first run
<https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/1/console> has been
triggered by the admin job and it failed successfully and the Jira ticket
under test <https://issues.apache.org/jira/browse/OOZIE-3608> was updated
as well.
I think we can call it a day for the Jenkins migration.

Thanks for the input and please file a ticket or call out if you encounter
any issues regarding the new pre-commit job.

gp

On Wed, Jul 22, 2020 at 6:18 PM Gézapeti Cseh <ge...@apache.org> wrote:

> Hey,
>
> After a short discussion on private@ (see the initial mail below) we've
> decided to move the jobs 6) and 7) over.
>
> I'd like to ask the Hadoop mailing list so Oozie can join the
> https://ci-hadoop.apache.org/  folder and use Hadoop's infrastructure (and
> pre-commit stuff) going forward just like we do today.
> Please let me know if there are any objections.
> Thanks
> gp
> ---------- Forwarded message ---------
> From: Gézapeti Cseh <ge...@apache.org>
> Date: Thu, Jul 16, 2020 at 8:24 PM
> Subject: Fwd: [IMPORTANT] - Migration to ci-builds.a.o
> To: <pr...@oozie.apache.org>
>
>
> Hey Oozie PMC!
>
> I've come across this mail on the builds@ list.
> I've found the following jobs on the old servers related to Oozie:
>
>    1. oozie-master-testing
>    <https://builds.apache.org/search/?q=oozie-master-testing>
>    2. oozie-trunk-w-hadoop-1
>    <https://builds.apache.org/search/?q=oozie-trunk-w-hadoop-1>
>    3. oozie-trunk-w-hadoop-2
>    <https://builds.apache.org/search/?q=oozie-trunk-w-hadoop-2>
>    4. oozie-trunk-precommit-build
>    <https://builds.apache.org/search/?q=oozie-trunk-precommit-build>
>    5. oozie-trunk-find-patches-available
>    <https://builds.apache.org/search/?q=oozie-trunk-find-patches-available
> >
>    6. PreCommit-OOZIE-Build
>    <https://builds.apache.org/search/?q=PreCommit-OOZIE-Build>
>    7. Oozie-flakytest-reproduction
>    <https://builds.apache.org/search/?q=Oozie-flakytest-reproduction>
>
>
> I think the only one that's worth migrating is 6) as it's kicked off by the
> pre-commit <https://builds.apache.org/job/PreCommit-Admin/> admin job not
> by 5).
>
> I'll try to do the migration, but I'd be happy if someone could join my
> adventures on the oozie Slack channel
> <https://the-asf.slack.com/archives/CDG1XSSTW>. I'm open to date
> suggestions :)
>
> Please let me know if 6) is sufficient or we have something else to
> migrate.
> thanks
> gp
>
> ---------- Forwarded message ---------
> From: Gavin McDonald <gm...@apache.org>
> Date: Thu, Jul 16, 2020 at 6:33 PM
> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> To: builds <bu...@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
>


-- 
*Peter Cseh* | Software Engineer, Cloudera Search
cloudera.com <https://www.cloudera.com>
[image: Cloudera] <https://www.cloudera.com/>
[image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
Cloudera on Facebook] <https://www.facebook.com/cloudera> [image: Cloudera
on LinkedIn] <https://www.linkedin.com/company/cloudera>
<https://www.cloudera.com/>
------------------------------

On Wed, Jul 22, 2020 at 6:18 PM Gézapeti Cseh <ge...@apache.org> wrote:

>
> Hey,
>
> After a short discussion on private@ (see the initial mail below) we've
> decided to move the jobs 6) and 7) over.
>
> I'd like to ask the Hadoop mailing list so Oozie can join the
> https://ci-hadoop.apache.org/  folder and use Hadoop's infrastructure
> (and pre-commit stuff) going forward just like we do today.
> Please let me know if there are any objections.
> Thanks
> gp
> ---------- Forwarded message ---------
> From: Gézapeti Cseh <ge...@apache.org>
> Date: Thu, Jul 16, 2020 at 8:24 PM
> Subject: Fwd: [IMPORTANT] - Migration to ci-builds.a.o
> To: <pr...@oozie.apache.org>
>
>
> Hey Oozie PMC!
>
> I've come across this mail on the builds@ list.
> I've found the following jobs on the old servers related to Oozie:
>
>    1. oozie-master-testing
>    <https://builds.apache.org/search/?q=oozie-master-testing>
>    2. oozie-trunk-w-hadoop-1
>    <https://builds.apache.org/search/?q=oozie-trunk-w-hadoop-1>
>    3. oozie-trunk-w-hadoop-2
>    <https://builds.apache.org/search/?q=oozie-trunk-w-hadoop-2>
>    4. oozie-trunk-precommit-build
>    <https://builds.apache.org/search/?q=oozie-trunk-precommit-build>
>    5. oozie-trunk-find-patches-available
>    <https://builds.apache.org/search/?q=oozie-trunk-find-patches-available>
>    6. PreCommit-OOZIE-Build
>    <https://builds.apache.org/search/?q=PreCommit-OOZIE-Build>
>    7. Oozie-flakytest-reproduction
>    <https://builds.apache.org/search/?q=Oozie-flakytest-reproduction>
>
>
> I think the only one that's worth migrating is 6) as it's kicked off by
> the pre-commit <https://builds.apache.org/job/PreCommit-Admin/> admin job
> not by 5).
>
> I'll try to do the migration, but I'd be happy if someone could join my
> adventures on the oozie Slack channel
> <https://the-asf.slack.com/archives/CDG1XSSTW>. I'm open to date
> suggestions :)
>
> Please let me know if 6) is sufficient or we have something else to
> migrate.
> thanks
> gp
>
> ---------- Forwarded message ---------
> From: Gavin McDonald <gm...@apache.org>
> Date: Thu, Jul 16, 2020 at 6:33 PM
> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> To: builds <bu...@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
>
>
>
>
>
>

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

Posted by Gézapeti Cseh <ge...@apache.org>.

Hey,

After a short discussion on private@ (see the initial mail below) we've
decided to move the jobs 6) and 7) over.

I'd like to ask the Hadoop mailing list so Oozie can join the
https://ci-hadoop.apache.org/  folder and use Hadoop's infrastructure (and
pre-commit stuff) going forward just like we do today.
Please let me know if there are any objections.
Thanks
gp
---------- Forwarded message ---------
From: Gézapeti Cseh <ge...@apache.org>
Date: Thu, Jul 16, 2020 at 8:24 PM
Subject: Fwd: [IMPORTANT] - Migration to ci-builds.a.o
To: <pr...@oozie.apache.org>


Hey Oozie PMC!

I've come across this mail on the builds@ list.
I've found the following jobs on the old servers related to Oozie:

   1. oozie-master-testing
   <https://builds.apache.org/search/?q=oozie-master-testing>
   2. oozie-trunk-w-hadoop-1
   <https://builds.apache.org/search/?q=oozie-trunk-w-hadoop-1>
   3. oozie-trunk-w-hadoop-2
   <https://builds.apache.org/search/?q=oozie-trunk-w-hadoop-2>
   4. oozie-trunk-precommit-build
   <https://builds.apache.org/search/?q=oozie-trunk-precommit-build>
   5. oozie-trunk-find-patches-available
   <https://builds.apache.org/search/?q=oozie-trunk-find-patches-available>
   6. PreCommit-OOZIE-Build
   <https://builds.apache.org/search/?q=PreCommit-OOZIE-Build>
   7. Oozie-flakytest-reproduction
   <https://builds.apache.org/search/?q=Oozie-flakytest-reproduction>


I think the only one that's worth migrating is 6) as it's kicked off by the
pre-commit <https://builds.apache.org/job/PreCommit-Admin/> admin job not
by 5).

I'll try to do the migration, but I'd be happy if someone could join my
adventures on the oozie Slack channel
<https://the-asf.slack.com/archives/CDG1XSSTW>. I'm open to date
suggestions :)

Please let me know if 6) is sufficient or we have something else to migrate.
thanks
gp

---------- Forwarded message ---------
From: Gavin McDonald <gm...@apache.org>
Date: Thu, Jul 16, 2020 at 6:33 PM
Subject: [IMPORTANT] - Migration to ci-builds.a.o
To: builds <bu...@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