project-config/jenkins/jobs/windmill.yaml
Khai Do d679cf6e01 rename 'tox' macro to 'run-tox'
JJB already has a tox module[1].  Defining a macro with the same name is
confusing and may cause problems when attempting to use this macro
elsewhere. Renaming it to something else should clear things up.

This is the warning from JJB:

$ jenkins-jobs test -o out ../project-config/jenkins/jobs
WARNING:jenkins_jobs.registry:You have a macro ('tox') defined for
'builder' component type that is masking an inbuilt definition

[1] http://docs.openstack.org/infra/jenkins-job-builder/builders.html#builders.tox

Change-Id: I6946229f6e94a5f4c10d6a5fc3b7049adeacacb1
2016-11-15 11:54:16 +01:00

54 lines
1.3 KiB
YAML

- builder:
name: windmill-checkout
builders:
- shell: |
#!/bin/bash -xe
CLONEMAP=`mktemp`
function cleanup {
rm -f $CLONEMAP
}
trap cleanup EXIT
cat > $CLONEMAP << EOF
clonemap:
- name: openstack/windmill
dest: .
EOF
/usr/zuul-env/bin/zuul-cloner -m $CLONEMAP --cache-dir /opt/git \
git://git.openstack.org openstack/windmill
- job-template:
name: '{pipeline}-windmill-{scenario}-{ostype}{job-suffix}'
node: '{ostype}'
builders:
- print-template-name:
template-name: "{template-name}"
- windmill-checkout
- run-tox:
envlist: "{scenario}"
publishers:
- console-log
- job-group:
name: 'windmill-jobs'
jobs:
- '{pipeline}-windmill-{scenario}-{ostype}{job-suffix}':
job-suffix: '-nv'
ostype:
- centos-7
- ubuntu-trusty
- ubuntu-xenial
pipeline: gate
scenario:
- deploy
- '{pipeline}-windmill-{scenario}-{ostype}{job-suffix}':
job-suffix: ''
ostype:
- centos-7
- ubuntu-trusty
- ubuntu-xenial
pipeline: gate
scenario:
- deploy