openstack
/
project-config
Code Issues Proposed changes

Switch TripleO scenario upgrade jobs to nv 

These jobs consistently timeout and we're working to move them out of
upstream to a 3rd party configuration. For now let's switch them to
non-voting so we can stop blocking the ocata patches.

Change-Id: Ibe89019a5b788fb9fcea1b721cc8e25a54f8ea8a
This commit is contained in:
Alex Schultz 2017-10-09 11:28:12 -06:00
parent 011ac0887c
commit ead9e7634c
2 changed files with 15 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
jenkins/jobs/projects.yaml
View File

@ -13014,9 +13014,7 @@
# duplicate scenarioXXX-multinode for upgrade scenarios
- '{trigger}-tripleo-ci-{jobname}{suffix}':
jobname: 'centos-7-scenario001-multinode'
suffix:
- '-upgrades'
- '-upgrades-nv'
suffix: '-upgrades-nv'
type: 'scenario001-multinode-upgrades'
node: centos-7-2-node
trigger: 'gate'
@ -13024,9 +13022,7 @@
timeout: 190
- '{trigger}-tripleo-ci-{jobname}{suffix}':
jobname: 'centos-7-scenario002-multinode'
suffix:
- '-upgrades'
- '-upgrades-nv'
suffix: '-upgrades-nv'
type: 'scenario002-multinode-upgrades'
node: centos-7-2-node
trigger: 'gate'
@ -13034,9 +13030,7 @@
timeout: 190
- '{trigger}-tripleo-ci-{jobname}{suffix}':
jobname: 'centos-7-scenario003-multinode'
suffix:
- '-upgrades'
- '-upgrades-nv'
suffix: '-upgrades-nv'
type: 'scenario003-multinode-upgrades'
node: centos-7-2-node
trigger: 'gate'

25
zuul/layout.yaml
View File

@ -803,24 +803,18 @@ project-templates:
- name: tripleo-upgrade-jobs-scenario001
check:
- gate-tripleo-ci-centos-7-scenario001-multinode-upgrades
- gate-tripleo-ci-centos-7-scenario001-multinode-upgrades-nv
- gate-tripleo-ci-centos-7-scenario001-multinode-oooq-container-upgrades-nv
gate:
- gate-tripleo-ci-centos-7-scenario001-multinode-upgrades
- name: tripleo-upgrade-jobs-scenario002
check:
- gate-tripleo-ci-centos-7-scenario002-multinode-upgrades
- gate-tripleo-ci-centos-7-scenario002-multinode-upgrades-nv
- gate-tripleo-ci-centos-7-scenario002-multinode-oooq-container-upgrades-nv
gate:
- gate-tripleo-ci-centos-7-scenario002-multinode-upgrades
- name: tripleo-upgrade-jobs-scenario003
check:
- gate-tripleo-ci-centos-7-scenario003-multinode-upgrades
- gate-tripleo-ci-centos-7-scenario003-multinode-upgrades-nv
- gate-tripleo-ci-centos-7-scenario003-multinode-oooq-container-upgrades-nv
gate:
- gate-tripleo-ci-centos-7-scenario003-multinode-upgrades
- name: tripleo-upgrade-jobs-scenario004
check:
@ -1939,10 +1933,15 @@ jobs:
- name: ^gate-tripleo-ci-centos-7-.*container.*$
branch: ^(?!stable/(newton|ocata)).*$
# TripleO Upgrade jobs are voting for scenario001,002,003 and
# classic multinode-upgrades job on Ocata.
# For now, we only want these jobs on stable/ocata in check & gate
- name: ^gate-tripleo-ci-centos-7(-scenario00(1|2|3))?-multinode-upgrades$
# TripleO Upgrade jobs are voting for the classic multinode-upgrades job on
# Ocata. For now, we only want these jobs on stable/ocata in check & gate
- name: ^gate-tripleo-ci-centos-7-multinode-upgrades$
branch: ^stable/ocata$
# TripleO Upgrade jobs are non-voting for scenario001,002,003 on Ocata.
# The scenario jobs take too long and have been switched to nv
# For now, we only want these jobs on stable/ocata in check
- name: ^gate-tripleo-ci-centos-7(-scenario00(1|2|3))-multinode-upgrades-nv$
branch: ^stable/ocata$
# Test TripleO stable/newton in Puppet OpenStack CI