You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Robbie Gemmell <ro...@gmail.com> on 2020/08/06 10:03:31 UTC
Re: [NOTICE] Jenkins CI server change, manual job migrations required
Reminder that the old system is being turned off on Aug 15th, migrate
any other jobs you want to be kept.
Also, disable old jobs when done migrating them to reflect demand
there, since the worker nodes are also being shifted across gradually
as appropriate.
Robbie
On Fri, 24 Jul 2020 at 13:29, Robbie Gemmell <ro...@gmail.com> wrote:
>
> The Jenkins setup at https://builds.apache.org is being replaced,
> including a server migration to a new Cloudbees hosted Jenkins primary
> at https://ci-builds.apache.org (both names will go there after the
> old setup is turned off).
>
> We must manually migrate any jobs we want to keep to the new system.
>
> The old system is being switched off on August 15th, but with worker
> nodes already gradually being migrated to the new setup now as
> appropriate to balance demand from new migrated jobs.
>
> I asked for a Qpid folder and for all committers to have access to the
> jobs, where they will live under:
> https://ci-builds.apache.org/job/Qpid/
>
> Our old jobs are at: https://builds.apache.org/view/M-R/view/Qpid/
>
> I plan to migrate all the Qpid JMS and Proton-J jobs myself and I've
> done a couple as a test. I don't plan on migrating most other jobs so
> if you want to keep them then please migrate them.
>
> Full initial details are at [1], with more in other threads on
> builds@a.o [2], such as the plugin installation request thread [3] for
> any required plugins not yet installed (not sure we have any
> requirements here though).
>
> Robbie
>
> [1] https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E
> [2] https://lists.apache.org/list.html?builds@apache.org
> [3] https://lists.apache.org/thread.html/r37c73263595b93c61c3d9b44e88a57f63edd28afa9aba3047259f4a4%40%3Cbuilds.apache.org%3E
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: [NOTICE] Jenkins CI server change, manual job migrations required
Posted by Robbie Gemmell <ro...@gmail.com>.
On Thu, 6 Aug 2020 at 17:18, Ganesh Murthy <gm...@redhat.com> wrote:
>
> On Thu, Aug 6, 2020 at 6:09 AM Robbie Gemmell <ro...@gmail.com>
> wrote:
>
> > Reminder that the old system is being turned off on Aug 15th, migrate
> > any other jobs you want to be kept.
> >
> > Also, disable old jobs when done migrating them to reflect demand
> > there, since the worker nodes are also being shifted across gradually
> > as appropriate.
> >
> > Robbie
> >
> > On Fri, 24 Jul 2020 at 13:29, Robbie Gemmell <ro...@gmail.com>
> > wrote:
> > >
> > > The Jenkins setup at https://builds.apache.org is being replaced,
> > > including a server migration to a new Cloudbees hosted Jenkins primary
> > > at https://ci-builds.apache.org (both names will go there after the
> > > old setup is turned off).
> > >
> > > We must manually migrate any jobs we want to keep to the new system.
> > >
> > > The old system is being switched off on August 15th, but with worker
> > > nodes already gradually being migrated to the new setup now as
> > > appropriate to balance demand from new migrated jobs.
> > >
> > > I asked for a Qpid folder and for all committers to have access to the
> > > jobs, where they will live under:
> > > https://ci-builds.apache.org/job/Qpid/
> > >
> > > Our old jobs are at: https://builds.apache.org/view/M-R/view/Qpid/
> > >
> > > I plan to migrate all the Qpid JMS and Proton-J jobs myself and I've
> > > done a couple as a test. I don't plan on migrating most other jobs so
> > > if you want to keep them then please migrate them.
> >
> Hi Robbie,
> I don't think this job needs to be migrated because we already have
> Travis builds taking care of this but I am interested in knowing
> your thoughts.
> https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Dispatch-Checks/
>
> Thanks.
>
I'd say thats fine. I created that job, and knowing that the Dispatch
folks dont bother with the Jenkins env and there are other builds
doing this check (Travis as you mention, and I also added it to the
new GitHub Actions build) I didn't intend to migrate it.
> >
> > > Full initial details are at [1], with more in other threads on
> > > builds@a.o [2], such as the plugin installation request thread [3] for
> > > any required plugins not yet installed (not sure we have any
> > > requirements here though).
> > >
> > > Robbie
> > >
> > > [1]
> > https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E
> > > [2] https://lists.apache.org/list.html?builds@apache.org
> > > [3]
> > https://lists.apache.org/thread.html/r37c73263595b93c61c3d9b44e88a57f63edd28afa9aba3047259f4a4%40%3Cbuilds.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > For additional commands, e-mail: users-help@qpid.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [NOTICE] Jenkins CI server change, manual job migrations required
Posted by Robbie Gemmell <ro...@gmail.com>.
On Thu, 6 Aug 2020 at 17:18, Ganesh Murthy <gm...@redhat.com> wrote:
>
> On Thu, Aug 6, 2020 at 6:09 AM Robbie Gemmell <ro...@gmail.com>
> wrote:
>
> > Reminder that the old system is being turned off on Aug 15th, migrate
> > any other jobs you want to be kept.
> >
> > Also, disable old jobs when done migrating them to reflect demand
> > there, since the worker nodes are also being shifted across gradually
> > as appropriate.
> >
> > Robbie
> >
> > On Fri, 24 Jul 2020 at 13:29, Robbie Gemmell <ro...@gmail.com>
> > wrote:
> > >
> > > The Jenkins setup at https://builds.apache.org is being replaced,
> > > including a server migration to a new Cloudbees hosted Jenkins primary
> > > at https://ci-builds.apache.org (both names will go there after the
> > > old setup is turned off).
> > >
> > > We must manually migrate any jobs we want to keep to the new system.
> > >
> > > The old system is being switched off on August 15th, but with worker
> > > nodes already gradually being migrated to the new setup now as
> > > appropriate to balance demand from new migrated jobs.
> > >
> > > I asked for a Qpid folder and for all committers to have access to the
> > > jobs, where they will live under:
> > > https://ci-builds.apache.org/job/Qpid/
> > >
> > > Our old jobs are at: https://builds.apache.org/view/M-R/view/Qpid/
> > >
> > > I plan to migrate all the Qpid JMS and Proton-J jobs myself and I've
> > > done a couple as a test. I don't plan on migrating most other jobs so
> > > if you want to keep them then please migrate them.
> >
> Hi Robbie,
> I don't think this job needs to be migrated because we already have
> Travis builds taking care of this but I am interested in knowing
> your thoughts.
> https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Dispatch-Checks/
>
> Thanks.
>
I'd say thats fine. I created that job, and knowing that the Dispatch
folks dont bother with the Jenkins env and there are other builds
doing this check (Travis as you mention, and I also added it to the
new GitHub Actions build) I didn't intend to migrate it.
> >
> > > Full initial details are at [1], with more in other threads on
> > > builds@a.o [2], such as the plugin installation request thread [3] for
> > > any required plugins not yet installed (not sure we have any
> > > requirements here though).
> > >
> > > Robbie
> > >
> > > [1]
> > https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E
> > > [2] https://lists.apache.org/list.html?builds@apache.org
> > > [3]
> > https://lists.apache.org/thread.html/r37c73263595b93c61c3d9b44e88a57f63edd28afa9aba3047259f4a4%40%3Cbuilds.apache.org%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > For additional commands, e-mail: users-help@qpid.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: [NOTICE] Jenkins CI server change, manual job migrations required
Posted by Ganesh Murthy <gm...@redhat.com>.
On Thu, Aug 6, 2020 at 6:09 AM Robbie Gemmell <ro...@gmail.com>
wrote:
> Reminder that the old system is being turned off on Aug 15th, migrate
> any other jobs you want to be kept.
>
> Also, disable old jobs when done migrating them to reflect demand
> there, since the worker nodes are also being shifted across gradually
> as appropriate.
>
> Robbie
>
> On Fri, 24 Jul 2020 at 13:29, Robbie Gemmell <ro...@gmail.com>
> wrote:
> >
> > The Jenkins setup at https://builds.apache.org is being replaced,
> > including a server migration to a new Cloudbees hosted Jenkins primary
> > at https://ci-builds.apache.org (both names will go there after the
> > old setup is turned off).
> >
> > We must manually migrate any jobs we want to keep to the new system.
> >
> > The old system is being switched off on August 15th, but with worker
> > nodes already gradually being migrated to the new setup now as
> > appropriate to balance demand from new migrated jobs.
> >
> > I asked for a Qpid folder and for all committers to have access to the
> > jobs, where they will live under:
> > https://ci-builds.apache.org/job/Qpid/
> >
> > Our old jobs are at: https://builds.apache.org/view/M-R/view/Qpid/
> >
> > I plan to migrate all the Qpid JMS and Proton-J jobs myself and I've
> > done a couple as a test. I don't plan on migrating most other jobs so
> > if you want to keep them then please migrate them.
>
Hi Robbie,
I don't think this job needs to be migrated because we already have
Travis builds taking care of this but I am interested in knowing
your thoughts.
https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Dispatch-Checks/
Thanks.
>
> > Full initial details are at [1], with more in other threads on
> > builds@a.o [2], such as the plugin installation request thread [3] for
> > any required plugins not yet installed (not sure we have any
> > requirements here though).
> >
> > Robbie
> >
> > [1]
> https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E
> > [2] https://lists.apache.org/list.html?builds@apache.org
> > [3]
> https://lists.apache.org/thread.html/r37c73263595b93c61c3d9b44e88a57f63edd28afa9aba3047259f4a4%40%3Cbuilds.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: [NOTICE] Jenkins CI server change, manual job migrations required
Posted by Robbie Gemmell <ro...@gmail.com>.
Ok, they decided to be nice and pushed it out a week so more could
migrate jobs easily, so one more update: the old setup is being shut
down on Sat 22nd
New: https://ci-builds.apache.org/job/Qpid/
Old: https://builds.apache.org/view/M-R/view/Qpid/
I have disabled all the now-migrated jobs on the old setup.
Robbie
On Thu, 13 Aug 2020 at 12:14, Robbie Gemmell <ro...@gmail.com> wrote:
>
> Final reminder, the old server is being turned off on Saturday 15th,
> any jobs not migrated will be lost.
>
> On Thu, 6 Aug 2020 at 11:03, Robbie Gemmell <ro...@gmail.com> wrote:
> >
> > Reminder that the old system is being turned off on Aug 15th, migrate
> > any other jobs you want to be kept.
> >
> > Also, disable old jobs when done migrating them to reflect demand
> > there, since the worker nodes are also being shifted across gradually
> > as appropriate.
> >
> > Robbie
> >
> > On Fri, 24 Jul 2020 at 13:29, Robbie Gemmell <ro...@gmail.com> wrote:
> > >
> > > The Jenkins setup at https://builds.apache.org is being replaced,
> > > including a server migration to a new Cloudbees hosted Jenkins primary
> > > at https://ci-builds.apache.org (both names will go there after the
> > > old setup is turned off).
> > >
> > > We must manually migrate any jobs we want to keep to the new system.
> > >
> > > The old system is being switched off on August 15th, but with worker
> > > nodes already gradually being migrated to the new setup now as
> > > appropriate to balance demand from new migrated jobs.
> > >
> > > I asked for a Qpid folder and for all committers to have access to the
> > > jobs, where they will live under:
> > > https://ci-builds.apache.org/job/Qpid/
> > >
> > > Our old jobs are at: https://builds.apache.org/view/M-R/view/Qpid/
> > >
> > > I plan to migrate all the Qpid JMS and Proton-J jobs myself and I've
> > > done a couple as a test. I don't plan on migrating most other jobs so
> > > if you want to keep them then please migrate them.
> > >
> > > Full initial details are at [1], with more in other threads on
> > > builds@a.o [2], such as the plugin installation request thread [3] for
> > > any required plugins not yet installed (not sure we have any
> > > requirements here though).
> > >
> > > Robbie
> > >
> > > [1] https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E
> > > [2] https://lists.apache.org/list.html?builds@apache.org
> > > [3] https://lists.apache.org/thread.html/r37c73263595b93c61c3d9b44e88a57f63edd28afa9aba3047259f4a4%40%3Cbuilds.apache.org%3E
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: [NOTICE] Jenkins CI server change, manual job migrations required
Posted by Robbie Gemmell <ro...@gmail.com>.
Ok, they decided to be nice and pushed it out a week so more could
migrate jobs easily, so one more update: the old setup is being shut
down on Sat 22nd
New: https://ci-builds.apache.org/job/Qpid/
Old: https://builds.apache.org/view/M-R/view/Qpid/
I have disabled all the now-migrated jobs on the old setup.
Robbie
On Thu, 13 Aug 2020 at 12:14, Robbie Gemmell <ro...@gmail.com> wrote:
>
> Final reminder, the old server is being turned off on Saturday 15th,
> any jobs not migrated will be lost.
>
> On Thu, 6 Aug 2020 at 11:03, Robbie Gemmell <ro...@gmail.com> wrote:
> >
> > Reminder that the old system is being turned off on Aug 15th, migrate
> > any other jobs you want to be kept.
> >
> > Also, disable old jobs when done migrating them to reflect demand
> > there, since the worker nodes are also being shifted across gradually
> > as appropriate.
> >
> > Robbie
> >
> > On Fri, 24 Jul 2020 at 13:29, Robbie Gemmell <ro...@gmail.com> wrote:
> > >
> > > The Jenkins setup at https://builds.apache.org is being replaced,
> > > including a server migration to a new Cloudbees hosted Jenkins primary
> > > at https://ci-builds.apache.org (both names will go there after the
> > > old setup is turned off).
> > >
> > > We must manually migrate any jobs we want to keep to the new system.
> > >
> > > The old system is being switched off on August 15th, but with worker
> > > nodes already gradually being migrated to the new setup now as
> > > appropriate to balance demand from new migrated jobs.
> > >
> > > I asked for a Qpid folder and for all committers to have access to the
> > > jobs, where they will live under:
> > > https://ci-builds.apache.org/job/Qpid/
> > >
> > > Our old jobs are at: https://builds.apache.org/view/M-R/view/Qpid/
> > >
> > > I plan to migrate all the Qpid JMS and Proton-J jobs myself and I've
> > > done a couple as a test. I don't plan on migrating most other jobs so
> > > if you want to keep them then please migrate them.
> > >
> > > Full initial details are at [1], with more in other threads on
> > > builds@a.o [2], such as the plugin installation request thread [3] for
> > > any required plugins not yet installed (not sure we have any
> > > requirements here though).
> > >
> > > Robbie
> > >
> > > [1] https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E
> > > [2] https://lists.apache.org/list.html?builds@apache.org
> > > [3] https://lists.apache.org/thread.html/r37c73263595b93c61c3d9b44e88a57f63edd28afa9aba3047259f4a4%40%3Cbuilds.apache.org%3E
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [NOTICE] Jenkins CI server change, manual job migrations required
Posted by Robbie Gemmell <ro...@gmail.com>.
Final reminder, the old server is being turned off on Saturday 15th,
any jobs not migrated will be lost.
On Thu, 6 Aug 2020 at 11:03, Robbie Gemmell <ro...@gmail.com> wrote:
>
> Reminder that the old system is being turned off on Aug 15th, migrate
> any other jobs you want to be kept.
>
> Also, disable old jobs when done migrating them to reflect demand
> there, since the worker nodes are also being shifted across gradually
> as appropriate.
>
> Robbie
>
> On Fri, 24 Jul 2020 at 13:29, Robbie Gemmell <ro...@gmail.com> wrote:
> >
> > The Jenkins setup at https://builds.apache.org is being replaced,
> > including a server migration to a new Cloudbees hosted Jenkins primary
> > at https://ci-builds.apache.org (both names will go there after the
> > old setup is turned off).
> >
> > We must manually migrate any jobs we want to keep to the new system.
> >
> > The old system is being switched off on August 15th, but with worker
> > nodes already gradually being migrated to the new setup now as
> > appropriate to balance demand from new migrated jobs.
> >
> > I asked for a Qpid folder and for all committers to have access to the
> > jobs, where they will live under:
> > https://ci-builds.apache.org/job/Qpid/
> >
> > Our old jobs are at: https://builds.apache.org/view/M-R/view/Qpid/
> >
> > I plan to migrate all the Qpid JMS and Proton-J jobs myself and I've
> > done a couple as a test. I don't plan on migrating most other jobs so
> > if you want to keep them then please migrate them.
> >
> > Full initial details are at [1], with more in other threads on
> > builds@a.o [2], such as the plugin installation request thread [3] for
> > any required plugins not yet installed (not sure we have any
> > requirements here though).
> >
> > Robbie
> >
> > [1] https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E
> > [2] https://lists.apache.org/list.html?builds@apache.org
> > [3] https://lists.apache.org/thread.html/r37c73263595b93c61c3d9b44e88a57f63edd28afa9aba3047259f4a4%40%3Cbuilds.apache.org%3E
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: [NOTICE] Jenkins CI server change, manual job migrations required
Posted by Robbie Gemmell <ro...@gmail.com>.
Final reminder, the old server is being turned off on Saturday 15th,
any jobs not migrated will be lost.
On Thu, 6 Aug 2020 at 11:03, Robbie Gemmell <ro...@gmail.com> wrote:
>
> Reminder that the old system is being turned off on Aug 15th, migrate
> any other jobs you want to be kept.
>
> Also, disable old jobs when done migrating them to reflect demand
> there, since the worker nodes are also being shifted across gradually
> as appropriate.
>
> Robbie
>
> On Fri, 24 Jul 2020 at 13:29, Robbie Gemmell <ro...@gmail.com> wrote:
> >
> > The Jenkins setup at https://builds.apache.org is being replaced,
> > including a server migration to a new Cloudbees hosted Jenkins primary
> > at https://ci-builds.apache.org (both names will go there after the
> > old setup is turned off).
> >
> > We must manually migrate any jobs we want to keep to the new system.
> >
> > The old system is being switched off on August 15th, but with worker
> > nodes already gradually being migrated to the new setup now as
> > appropriate to balance demand from new migrated jobs.
> >
> > I asked for a Qpid folder and for all committers to have access to the
> > jobs, where they will live under:
> > https://ci-builds.apache.org/job/Qpid/
> >
> > Our old jobs are at: https://builds.apache.org/view/M-R/view/Qpid/
> >
> > I plan to migrate all the Qpid JMS and Proton-J jobs myself and I've
> > done a couple as a test. I don't plan on migrating most other jobs so
> > if you want to keep them then please migrate them.
> >
> > Full initial details are at [1], with more in other threads on
> > builds@a.o [2], such as the plugin installation request thread [3] for
> > any required plugins not yet installed (not sure we have any
> > requirements here though).
> >
> > Robbie
> >
> > [1] https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E
> > [2] https://lists.apache.org/list.html?builds@apache.org
> > [3] https://lists.apache.org/thread.html/r37c73263595b93c61c3d9b44e88a57f63edd28afa9aba3047259f4a4%40%3Cbuilds.apache.org%3E
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [NOTICE] Jenkins CI server change, manual job migrations required
Posted by Ganesh Murthy <gm...@redhat.com>.
On Thu, Aug 6, 2020 at 6:09 AM Robbie Gemmell <ro...@gmail.com>
wrote:
> Reminder that the old system is being turned off on Aug 15th, migrate
> any other jobs you want to be kept.
>
> Also, disable old jobs when done migrating them to reflect demand
> there, since the worker nodes are also being shifted across gradually
> as appropriate.
>
> Robbie
>
> On Fri, 24 Jul 2020 at 13:29, Robbie Gemmell <ro...@gmail.com>
> wrote:
> >
> > The Jenkins setup at https://builds.apache.org is being replaced,
> > including a server migration to a new Cloudbees hosted Jenkins primary
> > at https://ci-builds.apache.org (both names will go there after the
> > old setup is turned off).
> >
> > We must manually migrate any jobs we want to keep to the new system.
> >
> > The old system is being switched off on August 15th, but with worker
> > nodes already gradually being migrated to the new setup now as
> > appropriate to balance demand from new migrated jobs.
> >
> > I asked for a Qpid folder and for all committers to have access to the
> > jobs, where they will live under:
> > https://ci-builds.apache.org/job/Qpid/
> >
> > Our old jobs are at: https://builds.apache.org/view/M-R/view/Qpid/
> >
> > I plan to migrate all the Qpid JMS and Proton-J jobs myself and I've
> > done a couple as a test. I don't plan on migrating most other jobs so
> > if you want to keep them then please migrate them.
>
Hi Robbie,
I don't think this job needs to be migrated because we already have
Travis builds taking care of this but I am interested in knowing
your thoughts.
https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Dispatch-Checks/
Thanks.
>
> > Full initial details are at [1], with more in other threads on
> > builds@a.o [2], such as the plugin installation request thread [3] for
> > any required plugins not yet installed (not sure we have any
> > requirements here though).
> >
> > Robbie
> >
> > [1]
> https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E
> > [2] https://lists.apache.org/list.html?builds@apache.org
> > [3]
> https://lists.apache.org/thread.html/r37c73263595b93c61c3d9b44e88a57f63edd28afa9aba3047259f4a4%40%3Cbuilds.apache.org%3E
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>