[jsonb-dev] Fw: Fwd: Migration of EE4J Jenkins instances from CJE to JIR

["Nathan Rauh" <nathan.rauh@xxxxxxxxxx>]

I am forwarding a
notice about a change to the Jenkins continuous integration for JSON-B
(and other Jakarta projects) which was initially sent to a more limited
audience, but with instructions to communicate it on to the committer group
and report any issues that we run into.

Here is a direct
link to the new continuous integration that has been set up for JSON-B,
https://ci.eclipse.org/jsonb

The following
issue exists to document any issues that we run into when trying it out,
https://bugs.eclipse.org/bugs/show_bug.cgi?id=551871

I tried submitting
a couple of builds with no changes, which seemed to run successfully.
Please give it
a try, especially as code updates are worked on, so that any issues can
be surfaced before they make the switch.

Thanks everyone!

-----
Forwarded by Nathan Rauh/Rochester/IBM on 12/03/2019 12:20 PM -----

From:
       Ed
Bratt <ed.bratt@xxxxxxxxxx>
To:
       Raymond
Auge <raymond.auge@xxxxxxxxxxx>, "Steve Millidge (Payara)"
<steve.millidge@xxxxxxxxxxx>, David Blevins <dblevins@xxxxxxxxxxxxx>,
arjan tijms <arjan.tijms@xxxxxxxxx>, "SHANNON,WILLIAM"
<bill.shannon@xxxxxxxxxx>, "DMITRY.KORNILOV" <dmitry.kornilov@xxxxxxxxxx>,
Santiago Pericas-Geertsen <santiago.pericasgeertsen@xxxxxxxxxx>,
hunting@xxxxxxxxxx, nathan.rauh@xxxxxxxxxx, Mark Thomas <markt@xxxxxxxxxx>,
zhijun Ren <ren.zhijun@xxxxxxxxxx>, Tom Jenkinson <tom.jenkinson@xxxxxxxxxx>,
gregw@xxxxxxxxxxx
Cc:
       Frederic
Gurr <frederic.gurr@xxxxxxxxxxxxxxxxxxxxxx>, Denis Roy <denis.roy@xxxxxxxxxxxxxxxxxxxxxx>,
"Mikaël Barbero" <mikael.barbero@xxxxxxxxxxxxxxxxxxxxxx>
Date:
       11/27/2019
05:11 PM
Subject:
       [EXTERNAL]
Fwd: Migration of EE4J Jenkins instances from CJE to JIRO

---

Hi there,
Eclipse is in the process of migrating
some Jenkins CI instances to a new CI cluster. Everyone listed in the "To"
of this message have been assigned one or more issues associated with this
work. Please read the forwarded e-mail, below.
As lead, you are not required to do the
work listed in the issues, but you should coordinate with your committer
team to assure that the migration has been completed and that the new CI
systems are up and running. Also, please don't forget to check that releases
and any work that integrates with external resources (like GitHub pre-integration
checks) are updated as well.
There is an FAQ regarding the general
effort, here.
You should have received a notice when the issue was assigned to you. For
your reference the master issue listing all impacted and incomplete projects
is here.
The issues contain some details specific to your projects. Please use the
issue comments if you encounter any difficulties or gaps so that the Admins
can take appropriate action. When everything is ready to do, please indicate
that via the issue for your project.
Thanks,
-- Ed Bratt


-------- Forwarded Message --------

Subject:	Migration of EE4J Jenkins instances from CJE to JIRO
Date:	Mon, 18 Nov 2019 19:54:14 +0100
From:	Frederic Gurr <frederic.gurr@xxxxxxxxxxxxxxxxxxxxxx>
Organization:	Eclipse Foundation
To:	Ed J Bratt <ed.bratt@xxxxxxxxxx>, Dmitry Kornilov <dmitry.kornilov@xxxxxxxxxx>
CC:	Denis Roy <denis.roy@xxxxxxxxxxxxxxxxxxxxxx>, Mikael Barbero <mikael.barbero@xxxxxxxxxxxxxxxxxxxxxx>

Hi Ed & Dmitry,

As announced on the ee4j-build mailing list, we are in the process of
migrating all EE4J Jenkins instances from CloudBees Jenkins Enterprise
(CJE) to JIRO (our custom tailored cluster based infra).
Most of the JIPPs have been migrated. About 10 Jenkins instances are
left and will be done before the end of November.

We need the approval of each project that everything works as expected
on the new environment (JIRO). In most cases this comes to down to
running the builds and checking if everything works as before. In some
cases Jenkinsfiles need to be adjusted.

So far no EE4J project has replied to the related Bugzilla issues (they
can be found here:
https://bugs.eclipse.org/bugs/showdependencytree.cgi?id=551832&hide_resolved=1)
with regards to acknowledging the successful migration.

We have a hard deadline in January, since the license for CJE will be
terminated and not be extended. Hence, time is running out. We'd really
like this to be mostly done before the holidays.

We'd appreciate your help with spreading this to all EE4J projects with
the required urgency, since Bugzilla issues assigned to the project
leads and reminders on the ee4j-build mailing list seemed to have been
ignored.


Regards,

Fred

-- 
Frederic Gurr
Release Engineer | Eclipse Foundation Europe GmbH

Annastr. 46, D-64673 Zwingenberg
Handelsregister: Darmstadt HRB 92821
Managing Directors: Ralph Mueller, Mike Milinkovich, Gaël Blondelle