[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cbi-dev] Update on HIPP to JIPP migration status
|
Hi Dani,
pom files should not include CI server specific configurations, so no it
_should_ not require any changes.
If you're referring to the Eclipse LTS Hudson instances, they will
eventually be migrated as well, but they are not a priority at the moment.
Regards,
Fred
On 13.02.2017 15:57, Daniel Megert wrote:
> Hi Fred
>
> From your e-mail I conclude that no changes are required to pom files.
> Is that correct?
>
> What is the plan for Eclipse LTS?
>
> Dani
>
>
>
> From: Frederic Gurr <frederic.gurr@xxxxxxxxxxx>
> To: Common-build Developers discussion <cbi-dev@xxxxxxxxxxx>
> Date: 10.02.2017 18:49
> Subject: [cbi-dev] Update on HIPP to JIPP migration status
> Sent by: cbi-dev-bounces@xxxxxxxxxxx
> ------------------------------------------------------------------------
>
>
>
> Hi,
>
> Just to give you a long overdue update on this topic, here is what's
> happening at the moment.
>
> - As of the beginning of 2017 we will not provision any new Hudson
> instances, unless there's a special request and requirements that can
> not be met with Jenkins. So if a project requests a new CI instance,
> they will get Jenkins by default (the latest LTS version at that time).
>
> - We are in the finishing stages for a little tool that helps to convert
> the Hudson config file structure to the Jenkins config file structure.
> So when Hudson is replaced with Jenkins, most of the configuration still
> works. We will test this with a few guinea pig projects in the coming weeks.
>
> - Once that converter tool is battle tested, we will convert a certain
> number of smaller HIPPs (or HIPPs with simple jobs) first (e.g. 5 per
> week) and ramp up when possible. We will do this to reduce the risk and
> possible impacts of any roadblocks that we might face.
>
> - In the last stage we will convert HIPPs that are part of the SimRel
> and essential like the Shared or Platform HIPP.
>
> We can't give an exact time line for the whole HIPP to JIPP migration,
> but be assured that this is one of the main objectives in Eclipse CBI
> for 2017.
>
>
> Please let me know, If you have any concerns, suggestions, etc. or
> comment on bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=336262
>
>
> Regards,
>
> Fred
>
>
> --
> Frederic Gurr
>
> Release Engineer
> Eclipse Foundation
> _______________________________________________
> cbi-dev mailing list
> cbi-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cbi-dev
>
>
>
>
>
>
> _______________________________________________
> cbi-dev mailing list
> cbi-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cbi-dev
>