Re-implement standard-CI with pipelines (V2)
Description
blocks
is blocked by
relates to
Activity
Barak Korren June 10, 2018 at 3:03 PM
All blockers for this ticket were resolved, and we now have a full pipeline-based implementations of all aspects of STDCI.
Barak Korren May 13, 2018 at 11:42 AM
Removing https://ovirt-jira.atlassian.net/browse/OVIRT-1876#icft=OVIRT-1876 as a blocker as we're not planning on implementing it soon and https://ovirt-jira.atlassian.net/browse/OVIRT-1955#icft=OVIRT-1955 will serve as a replacement making pipeline-based poll-upstream-sources jobs without nproviding support for making them dynamically from the STDCI DSL.
Eyal Edri May 13, 2018 at 11:31 AM
+1, looks like most of the work is done indeed
Barak Korren May 13, 2018 at 11:16 AM
@Eyal Edri The blockers for this are in progress; I'm considering moving this to "done" even though we're not 100% pipeline-based as I intended when I first created this, but I'm not sure we'll fully implement https://ovirt-jira.atlassian.net/browse/OVIRT-1876#icft=OVIRT-1876 soon and might as well track it on its own.
Eyal Edri May 13, 2018 at 10:55 AM
@Barak Korren I believe this isn't 'in progress'? can we move it back to TODO?
The Standard-CI system job in Jenkins are currently implemented using "Free-Style" Jenkins jobs, if we could re-implement them with Jenkins pipelines, if will enable us to use cleaner code and also have many features that may be to hard to implement with "Free-Style" jobs.
Tickets that specify features that will probably require using pipelines will linkt to this ticket as a blocker.