openstack/grenade
Code Issues Proposed changes

Update the master grenade setting for yoga to master upgrade

Browse Source 
Change-Id: I076ee646ca0e017748a0eeba715e5604ec6b68eb
This commit is contained in:
Martin Kopec 2022-03-25 14:48:58 +01:00 committed by Ghanshyam
parent e10ac41b71
commit b960348631
2 changed files with 12 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
.zuul.yaml
View File

@ -376,6 +376,17 @@
Grenade job that skips a release, validating that deployers can skip
specific releases as prescribed by our process.
parent: grenade
# NOTE(gmann): This job is meant to validate the tick to tick release
# upgrade so supposed to run on tick release gate only. To make sure
# that, when the current master is tock release, below branch variant will
# stop running it on tock release master. And once new tick release start
# (means the current master is tick release), we need to remove the below
# branch variant condition so that it again start running on tick release
# master gate.
# Along with grenade gate, this job runs on many other projects gate
# also and in this job definition, we control for everyone to run on tick
# release only.
branches: ^(?!master).*$
vars:
# Move this forward when master changes to a new skip-level-allowed
# target release. Right now, this is wallaby because master is yoga.

2
roles/configure-grenade-branches/defaults/main.yaml
View File

@ -1,3 +1,3 @@
---
grenade_from_branch: stable/xena
grenade_from_branch: stable/yoga
grenade_to_branch: master