cloud-infra: Reduce the frequency of heat based jobs to minimum 06/3206/2
authorFatih Degirmenci <fdegir@gmail.com>
Tue, 17 Dec 2019 09:24:57 +0000 (10:24 +0100)
committerFatih Degirmenci <fdegir@gmail.com>
Tue, 17 Dec 2019 09:33:38 +0000 (10:33 +0100)
commit21b1a83629249db48eaf345595cc2cc3fddafc1f
tree7500672516627a1c56f2b4cdedd531fbc60a53cd
parent1ffd4ffa67290a9bf1901d2a64f14a6b844b8060
cloud-infra: Reduce the frequency of heat based jobs to minimum

Due to stability issues with CityCloud heat stack creation, we
need to limit running heat based jobs to minimum since there is
no reason anymore to run jobs automatically without hearing from
City Support first.

Here is what is done for the jobs per stack:

- ONAP Pipelines: nightly triggers for ONAP Master and ElAlto
branches have been disabled. This means that they can still be
triggered manually if needed. [0][1]
- Engine Verification Heat Jobs: voting for these jobs have been
disabled. This means that they will still be triggered when a new
patch is sent for review but their vote will not be used when
calculating the verdict. [2]
- Spinnaker Pipelines: nightly triggers for Spinnaker 1.16 pipelines
have been disabled. This means that they can still be triggered
manually if needed. [3]

[0] https://jenkins.nordix.org/job/onap-online-full-ubuntu1804-kubespray-city-cloud-daily-master/
[1] https://jenkins.nordix.org/job/onap-online-full-ubuntu1804-kubespray-city-cloud-daily-elalto/
[2] https://jenkins.nordix.org/job/cloud-infra-verify-engine-ubuntu1804-city-cloud-master/
[3] https://jenkins.nordix.org/job/k8-calico-spinnaker-ubuntu1804-kubespray-city-cloud-daily-1.16/

Change-Id: I070a38194fcf6eff17fe114c29493af2323073fc
jjb/cloud-infra/cloud-infra-engine-verify-deploy.yaml
jjb/cloud-infra/cloud-infra-periodic-onap.yaml
jjb/cloud-infra/cloud-infra-periodic-spinnaker.yaml