|
Duplicate fuel-verify jobs based on cluster type (virtual, baremetal)
and allow (re)checking changes using a specific scenario:
- ALL changes will trigger a virtual POD CI cycle (build, deploy,
smoke) on submit, rebase etc., just like they used to;
- change comments containing a substring formatted like:
* `recheck: os-odl-nofeature-ha`
* `reverify: os-odl-nofeature-noha`
* `recheck`
will trigger only virtual or baremetal deployments of the required
scenario (default os-nosdn-nofeature-noha) on:
* virtual PODs if scenario is NOHA;
* baremetal PODs if scenario is HA;
- limit arm64 verify job running on arm-virtual2 to the installation
of infrastructure VMs and skip cluster setup to prevent POD time
starvation;
Limitations:
- HA scenarios can only be verified on manual request via a change
comment (e.g. 'recheck: os-odl-ovs-ha');
JIRA: FUEL-390
Change-Id: I6368cfd045180d6a7202b8d817b17a4b123ba2af
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
Alexandru Avadanii