Re: [cross-project-issues-dev] [ee4j-build] CI instances on jenkins.eclipse.org will be migrated to Jiro

[Frederic Gurr]

Hi,

The job configurations will be copied 1:1. As mentioned, a few things
need to be adjusted manually by the projects.

One thing that comes to mind is Maven settings files. They won't need to
be injected anymore, since they will be available as K8s secrets. If
custom containers are used, the container configurations will need to be
adjusted accordingly.

Regards,

Fred

On 24.09.19 20:31, Bill Shannon wrote:
> How will the configuration be migrated?
> 
> Will you be copying the configuration, with any adjustments needed for the
> new environment?  Or will we need to recreate each job from scratch?
> 
> Frederic Gurr wrote on 9/24/19 9:14 AM:
>> Hi,
>>
>> We will be migrating Jenkins CI instances off CJE to Jiro starting in
>> October 2019. CloudBees Jenkins Enterprise (CJE) is an enterprise CI
>> product by CloudBees, Jiro is our in-house OSS solution based on OSS
>> Jenkins, Docker, Jenkins Configuration as Code plugin and a few scripts.
>>
>> Since CJE is not flexible enough for our requirements, we won't be
>> renewing our license in the beginning of next year.
>>
>> Currently, 47 CI instances are hosted on https://jenkins.eclipse.org
>> that need to be migrated before the end of 2019. For most projects this
>> should be straight forward. CI instances on CJE are already running on
>> our cluster-based infrastructure and only a few configurations need to
>> be adapted. We will support the projects along the way and make sure
>> that disruptions are reduced to a minimum.
>>
>> We will open separate Bugzilla issues for each JIPP that track the
>> migration.
>>
>> Please let me know if you have any questions or concerns.
>>
>> 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
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Disk usage report for HIPP/JIPPs

[genie]

Compiled 2019-09-24-13:30:01

Projects exceeding 80G of disk space on HIPP/JIPPs:
===
365G /jobs/genie.packaging
111G /jobs/genie.platform
109G /jobs/genie.tracecompass
88G /jobs/genie.xtext
85G /jobs/genie.gemoc
82G /jobs/genie.ice
===

If you find your project's name in the above list, please check
your Hudson/Jenkins configuration and try to lower the disk usage.

You can find more information about CI best practices and disk usage
here: https://wiki.eclipse.org/CI_best_practices#Disk_usage.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] OI2JIRO migration - reminder - hipp4

[Frederic Gurr]

Hi,

The migration of both JIPPs is not complete yet, so it's technically not
a mistake. The reason why the last steps (retiring the old JIPP and
moving the new JIPPs back to ci.eclipse.org) are still missing, is on me
though. Both Bugzilla issues fell off my radar while waiting for M3.

I'll fix that now.

Regards,

Fred

On 24.09.19 18:38, Ed Willink wrote:
> HI
> 
> Some mistake surely?
> 
> "Only one(!)"
> 
> Both QVTd and QVTo are marked as RESOLVED FIXED.
> 
>     Regards
> 
>         Ed Willink
> 
> On 24/09/2019 16:39, Frederic Gurr wrote:
>> Hi,
>>
>> Unfortunately, there has been almost no progress on the migration of
>> JIPPs on hipp4: Only one(!) project acknowledged the migration in the
>> last month and a half. So we need to give this a gentle push:
>>
>> *** Please note: if we don't hear back from projects before Monday,
>> October 21st, 2019, we will assume silent agreement that the migration
>> was successful. We will then start to archive the JIPP on the old
>> infra. ***
>>
>>
>> Regards,
>>
>> Fred
>>
>> On 08.08.19 13:41, Frederic Gurr wrote:
>>> Hi,
>>>
>>> This is a gentle reminder to all projects whose JIPPs reside on hipp4 to
>>> check and acknowledge that the migration from the old infra to the new
>>> cluster based infra (codename Jiro) was successful.
>>>
>>> This concerns the following projects:
>>> * Ajdt
>>> * Apogy
>>> * App4mc
>>> * Chess
>>> * Diffmerge
>>> * Dirigible
>>> * Egerrit
>>> * Epsilon
>>> * ESF
>>> * Glassfish-tools
>>> * Henshin
>>> * Jubula
>>> * Keti
>>> * Mdht
>>> * Openk-platform
>>> * Qvt-oml
>>> * Qvtd
>>> * Vorto
>>>
>>> You can find the corresponding Bugzilla issues in the list here:
>>> https://bugs.eclipse.org/bugs/showdependencytree.cgi?id=544221_resolved=1
>>>
>>>
>>> Some of the projects are already actively involved, but the majority of
>>> projects has not responded at all. A lot of people are still on summer
>>> leave, so we know that things move slower around this time of the year.
>>>
>>> Once you're back, we appreciate your assistance in finishing this
>>> migration effort in a timely manner.
>>>
>>>
>>> Regards,
>>>
>>> Fred
>>>
>>>
> 
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
> 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

-- 
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
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] OI2JIRO migration - reminder - hipp4

[Ed Willink]

HI

Some mistake surely?

"Only one(!)"

Both QVTd and QVTo are marked as RESOLVED FIXED.

    Regards

        Ed Willink

On 24/09/2019 16:39, Frederic Gurr wrote:

Hi,

Unfortunately, there has been almost no progress on the migration of
JIPPs on hipp4: Only one(!) project acknowledged the migration in the
last month and a half. So we need to give this a gentle push:

*** Please note: if we don't hear back from projects before Monday,
October 21st, 2019, we will assume silent agreement that the migration
was successful. We will then start to archive the JIPP on the old infra. ***


Regards,

Fred

On 08.08.19 13:41, Frederic Gurr wrote:

Hi,

This is a gentle reminder to all projects whose JIPPs reside on hipp4 to
check and acknowledge that the migration from the old infra to the new
cluster based infra (codename Jiro) was successful.

This concerns the following projects:
* Ajdt
* Apogy
* App4mc
* Chess
* Diffmerge
* Dirigible
* Egerrit
* Epsilon
* ESF
* Glassfish-tools
* Henshin
* Jubula
* Keti
* Mdht
* Openk-platform
* Qvt-oml
* Qvtd
* Vorto

You can find the corresponding Bugzilla issues in the list here:
https://bugs.eclipse.org/bugs/showdependencytree.cgi?id=544221_resolved=1

Some of the projects are already actively involved, but the majority of
projects has not responded at all. A lot of people are still on summer
leave, so we know that things move slower around this time of the year.

Once you're back, we appreciate your assistance in finishing this
migration effort in a timely manner.


Regards,

Fred




---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] CI instances on jenkins.eclipse.org will be migrated to Jiro

[Frederic Gurr]

Hi,

We will be migrating Jenkins CI instances off CJE to Jiro starting in
October 2019. CloudBees Jenkins Enterprise (CJE) is an enterprise CI
product by CloudBees, Jiro is our in-house OSS solution based on OSS
Jenkins, Docker, Jenkins Configuration as Code plugin and a few scripts.

Since CJE is not flexible enough for our requirements, we won't be
renewing our license in the beginning of next year.

Currently, 47 CI instances are hosted on https://jenkins.eclipse.org
that need to be migrated before the end of 2019. For most projects this
should be straight forward. CI instances on CJE are already running on
our cluster-based infrastructure and only a few configurations need to
be adapted. We will support the projects along the way and make sure
that disruptions are reduced to a minimum.

We will open separate Bugzilla issues for each JIPP that track the
migration.

Please let me know if you have any questions or concerns.

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
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Nexus (repo.eclipse.org and repo.locationtech.org) maintenance

[Mikaël Barbero]

Hi,

We will have to perform some maintenance on repo.eclipse.org 
 and repo.locationtech.org 
 which may affect their availability and as such 
disturb some build jobs.

repo.locationtech.org  will be updated to latest 
version tomorrow Wed. 09/25 @ 11am CEST (5am EDT). If all goes well, it should 
be unavailable for less than 1 hour.

repo.eclipse.org  will also be updated to latest 
version tomorrow Wed. 09/25 @ 12am CEST (6am EDT). It should be equally 
unavailable for less than 1 hour.

repo.locationtech.org  will be moved to a new 
host on Fri. 09/27 @ 10am CEST (4am EDT). It should be unavailable for less 
than 2 hours.

Thanks for your patience during these maintenance windows.

Cheers,

Mikaël Barbero
Team Lead - Release Engineering | Eclipse Foundation
 (+33) 642 028 039 |  @mikbarbero
Eclipse Foundation : The Platform for Open Innovation 
and Collaboration



signature.asc
Description: Message signed with OpenPGP
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] OI2JIRO migration - reminder - hipp4

[Frederic Gurr]

Hi,

Unfortunately, there has been almost no progress on the migration of
JIPPs on hipp4: Only one(!) project acknowledged the migration in the
last month and a half. So we need to give this a gentle push:

*** Please note: if we don't hear back from projects before Monday,
October 21st, 2019, we will assume silent agreement that the migration
was successful. We will then start to archive the JIPP on the old infra. ***


Regards,

Fred

On 08.08.19 13:41, Frederic Gurr wrote:
> Hi,
> 
> This is a gentle reminder to all projects whose JIPPs reside on hipp4 to
> check and acknowledge that the migration from the old infra to the new
> cluster based infra (codename Jiro) was successful.
> 
> This concerns the following projects:
> * Ajdt
> * Apogy
> * App4mc
> * Chess
> * Diffmerge
> * Dirigible
> * Egerrit
> * Epsilon
> * ESF
> * Glassfish-tools
> * Henshin
> * Jubula
> * Keti
> * Mdht
> * Openk-platform
> * Qvt-oml
> * Qvtd
> * Vorto
> 
> You can find the corresponding Bugzilla issues in the list here:
> https://bugs.eclipse.org/bugs/showdependencytree.cgi?id=544221_resolved=1
> 
> Some of the projects are already actively involved, but the majority of
> projects has not responded at all. A lot of people are still on summer
> leave, so we know that things move slower around this time of the year.
> 
> Once you're back, we appreciate your assistance in finishing this
> migration effort in a timely manner.
> 
> 
> 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
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] OI2JIRO Migration status update

[Frederic Gurr]

Hi,

We are currently migrating Jenkins CI instances off our old
infrastructure onto our new cluster-based infrastructure.
The order is defined by the physical machines (hipp1-10) and we move
JIPPs machine by machine. Next up are JIPPs on hipp6.

More info about the why and how can be found here:
=> https://wiki.eclipse.org/CBI/Jenkins_Migration_FAQ

Here is a quick update on the current status:

Number of JIPPs on old infra:   184
Number of JIPPs that have been successfully migrated:46
Number of JIPPs that still wait for acknowledgement: 33
Number of JIPPs that are not migrated yet:   98

So we are close to the half-way mark. We're planning to wrap up the
migration in Q1 2020. While we do most of the heavy lifting, the
projects will need to check and acknowledge the migration in a timely
fashion to help us stick to the timeline.

We've gained a lot of experience about possible migration issues in the
past months and documented most common warnings/errors in the wiki here:
=> https://wiki.eclipse.org/Jenkins

Please let me know, if you have any questions or concerns.

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
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] ACTION REQUIRED: SimRel Participants Please Fix Your SimRel Contribution's Problems

[Ed Merks]

That's certainly the simplest approach, and that would work correctly 
today.  But should there ever by an EPL 3.0 along with a corresponding 
SUA 3.0, one would automatically pick that up without having made all 
the corresponding changes to the file headers.


One could avoid that using almost the same approach as what you've 
outlined but either lock in the license-feature-version to 
2.0.2.v20181016-2210 instead of 0.0.0 or lock in the repository to


http://download.eclipse.org/cbi/updates/license/2.0.2.v20181016-2210

instead of

  http://download.eclipse.org/cbi/updates/license

In any case, it really is a very simple problem to fix!


On 24.09.2019 11:03, Ed Willink wrote:

Hi

On 24/09/2019 06:38, Ed Merks wrote:

For example Eclipse Collections has this specific report:

https://download.eclipse.org/oomph/archive/simrel/collections.aggrcon/index.html 




Thanks Ed. An easy to consume report. Great job.
Note that the license problem, i.e.,  all the various corrupted 
versions of SUA 2.0, is easy to fix, e.g., I fixed it like this for 
the Platform:


https://git.eclipse.org/r/#/c/149636/1/eclipse.platform.releng.prereqs.sdk/eclipse-sdk-prereqs.target 



If you don't really care what version of the license you use, there is 
a simpler solution; re-use the CBI master license. Version 0.0.0 will 
redirect to the latest.


Each feature.xml:




   
  [Documentation] Copyright text will be taken from the shared 
license feature

   

Each *.target:

  includeMode="planner" includeSource="true" type="InstallableUnit">

    
    location="https://download.eclipse.org/cbi/updates/license"/>

  

If you have your own license feature, just delete it.

Regards

Ed Willink


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or 
unsubscribe from this list, visit

https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] ACTION REQUIRED: SimRel Participants Please Fix Your SimRel Contribution's Problems

[Ed Willink]

Hi

On 24/09/2019 06:38, Ed Merks wrote:

For example Eclipse Collections has this specific report:

https://download.eclipse.org/oomph/archive/simrel/collections.aggrcon/index.html 




Thanks Ed. An easy to consume report. Great job.
Note that the license problem, i.e.,  all the various corrupted 
versions of SUA 2.0, is easy to fix, e.g., I fixed it like this for 
the Platform:


https://git.eclipse.org/r/#/c/149636/1/eclipse.platform.releng.prereqs.sdk/eclipse-sdk-prereqs.target 



If you don't really care what version of the license you use, there is a 
simpler solution; re-use the CBI master license. Version 0.0.0 will 
redirect to the latest.


Each feature.xml:




   
  [Documentation] Copyright text will be taken from the shared 
license feature

   

Each *.target:

  includeMode="planner" includeSource="true" type="InstallableUnit">

    
    location="https://download.eclipse.org/cbi/updates/license"/>

  

If you have your own license feature, just delete it.

Regards

Ed Willink


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev