7fc9c616e1
The update-constraints job does not need to run on the signing node, so move it to the proposal nodes. Update the job patterns used to decide whether to take a node offline after a job runs to include update-constraints. Change-Id: Ieb25446ac7a679ef26f6c09971cb2eddf41d5178 Signed-off-by: Doug Hellmann <doug@doughellmann.com>
26 lines
862 B
YAML
26 lines
862 B
YAML
- job-template:
|
|
name: '{name}-pypi-both-upload'
|
|
node: release
|
|
|
|
builders:
|
|
- revoke-sudo
|
|
- gerrit-git-prep
|
|
- shell: |
|
|
# Note we upload the wheel first because pip prefers wheels
|
|
# and there is a mirroring issue where sometimes the first
|
|
# artifact uploaded is the only one you get. Since pip prefers
|
|
# wheels it is best to make the wheel the one we get.
|
|
/usr/local/jenkins/slave_scripts/pypi-wheel-upload.sh {name} tarballs.openstack.org
|
|
/usr/local/jenkins/slave_scripts/pypi-tarball-upload.sh {name} tarballs.openstack.org
|
|
|
|
publishers:
|
|
- console-log
|
|
|
|
- job-group:
|
|
name: pypi-jobs
|
|
jobs:
|
|
- '{name}-pypi-both-upload'
|
|
- '{name}-tarball'
|
|
- '{name}-tarball-signing'
|
|
- '{name}-announce-release'
|
|
- 'propose-{name}-update-constraints' |