Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] HIPP2JIPP migration and cascaded jobs

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
> 
> 


Back to the top