]
Barak Korren updated OVIRT-1013:
--------------------------------
Summary: Automate standard-CI job creation (was: Automate standard-CI job creation
(V2))
Automate standard-CI job creation
---------------------------------
Key: OVIRT-1013
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-1013
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: oVirt CI
Reporter: Barak Korren
Assignee: infra
Labels: standard-ci
The premise of the CI standard is simple: The developers place simple script in the
'automation' directory, and The infa team take care of making Jenkins run it when
it should.
But we haven't been able to fully deliver on this premise yet. Getting a project to
work with the CI standard also takes writing some YAML in the 'Jenkins' repo. Even
worse, this YAML needs to be maintained over time as new project branches get created, new
platforms get targeted, etc.
The core reason behind having to write YAML, is that there are two technical details that
we need to know in order to run the CI jobs, but are not specified in a way that allows
detecting them automatically. Those details are:
1. The platforms a certain project needs to be built and tested on.
2. The branches of the project that CI needs to look at, and how do they map to an oVirt
releases.
We need to specify a way to specify the details above in a way that will allow the CI
system to automatically detect them.