Re: [ee4j-build] CI instances on jenkins.eclipse.org will be migrated to

[Bill Shannon <bill.shannon@xxxxxxxxxx>]

So you'll simply remove all the injection of Maven settings file when you
copy the configuration?  Or will we need to remove that manually after
migration?

What all will need to be adjusted in custom container configuration?

I checked a few of our custom containers and the corresponding jobs and
I don't see how they currently handle injection of the Maven settings
file so I'm not sure what would need to be changed after migration.


Frederic Gurr wrote on 9/24/19 11:52 AM:
> 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
>>>
>