Re: [cross-project-issues-dev] HIPP2JIPP migration and cascaded jobs

[Florian Waibel <fwaibel@xxxxxxxxxxxxxxxxx>]

Hi,

I have changed all listed Virgo jobs to Cascading Job: None.

Regards,
  florian


> On 7. Feb 2018, at 19:02, Frederic Gurr <frederic.gurr@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> 
> Hi,
> 
> Unfortunately some projects still use cascaded jobs:
> 
> - shared
> - ep-unit-lin64
> - ep-unit-mac64
> - ep-unit-win32
> - ep47U-unit-win32
> - ep47Y-unit-lin64
> - ep47Y-unit-mac64
> - ep47Y-unit-win32
> - ep48I-unit-mac64
> - ep48I-unit-win32
> - ep47M-unit-mac64
> - ep47M-unit-win32
> - ep47U-unit-mac64
> 
> - virgo
> - virgo.documentation.snapshot
> - virgo.ide.snapshot
> - virgo.kernel-tools.snapshot
> - virgo.kernel.3.6.snapshot
> - virgo.packaging.3.6.snapshot
> - virgo.samples.snapshot
> - virgo.util.3.6.snapshot
> - virgo.web.3.6.snapshot
> 
> Please convert them to freestyle jobs immediately to not cause any
> delays in the Hudson to Jenkins migration.
> 
> Regards,
> 
> Fred
> 
> 
> On 17.01.2018 13:46, Frederic Gurr wrote:
>> Hi,
>> 
>> Since Jenkins does not support cascaded jobs, such jobs need to be
>> converted to normal freestyle jobs before a HIPP2JIPP migration.
>> 
>> A scan found the following projects that use cascaded jobs:
>> 
>> - diffmerge
>> - virgo
>> - mpc
>> - triquetrum
>> - tinydtls
>> - emfcompare
>> - mylyn
>> - shared
>> 
>> If your project is on this list, please convert any cascaded job to a
>> normal freestyle job by copying all configuration settings from the
>> parent job.
>> 
>> 
>> Please let me know, if you have any concerns or questions.
>> 
>> 
>> Regards,
>> 
>> Fred
>> 
>> 
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev