Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [openmq-dev] Fwd: Migration of EE4J Jenkins instances from CJE to JIRO

Werner,

If you can take the issue and just make sure that the builds work. I'm not sure if it's properly wired up everywhere it needs to be. Arjan may remember what was necessary to release OpenMQ for Eclipse GlassFish 5.1. Sorry, I don't know those details and it doesn't appear that the readme files have been updated (at least not those I checked).

(At the current moment, the old Jenkins system doesn't respond so I can't look at the older system results.)

Thanks,

-- Ed

On 11/28/2019 12:06 AM, Werner Keil wrote:
Ed,

I contributed to OpenMQ, so happy to help, unless Arjan really wants to?
He also has a couple of other projects like Faces or Security where he's actually the lead, so it would be Ok for me.

Regards,
Werner


Ed Bratt <ed.bratt@xxxxxxxxxx> schrieb am Do., 28. Nov. 2019, 00:20:

Werner or Arjan,

Could we impose on one or both of you to please check the CI migration for OpenMQ. We don't currently have a lead for this project. Only committer members can access/edit the CI system configurations so this needs to be done by someone that's already an Open MQ committer. The OpenMQ migration issue is: https://bugs.eclipse.org/bugs/show_bug.cgi?id=551885

(I'm also including the OpenMQ-Dev list on the chance that one of the other committer members would like to take this up.)

Thanks,

-- Ed



-------- Forwarded Message --------
Subject: Fwd: Migration of EE4J Jenkins instances from CJE to JIRO
Date: Wed, 27 Nov 2019 15:11:21 -0800
From: Ed Bratt <ed.bratt@xxxxxxxxxx>
Organization: Oracle Corporation
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>


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

Back to the top