project-config/jenkins/jobs/maven-plugin-jobs.yaml
Jeremy Stanley da67129d34 Remove pointless tarball-site parameter
Across the entirety of our job config corpus, we only ever set the
tarball-site parameter to tarballs.openstack.org. Instead just set
it directly in the publishers where it's needed and reduce
unwarranted confusion for people writing job configs. This also
allows us to get rid of the parameterized sites in the tarball,
wheel and war publishers.

Change-Id: I31109f41177b8c07177d7ed8ef16cbfd135131ef
2016-12-19 14:48:08 +00:00

61 lines
1.5 KiB
YAML

# usig a freestyle project to work around jenkins bug:
# https://issues.jenkins-ci.org/browse/JENKINS-14193
- job-template:
name: '{name}-localrepo-upload-{node}'
node: '{node}'
wrappers:
- build-timeout:
timeout: 30
- timestamps
builders:
- gerrit-git-prep
- install-distro-packages
- revoke-sudo
- shell: |
#!/bin/bash -xe
/usr/local/jenkins/slave_scripts/version-properties.sh
source version.properties
mvn clean package -Dproject-version=$PROJECT_VER
publishers:
- war:
warfile: 'target/{name}-*.jar'
target: 'tarballs/ci/{name}'
- console-log
- job-template:
name: '{name}-mavencentral-upload'
node: release
builders:
- revoke-sudo
- shell: |
#!/bin/bash -xe
TAG=`echo $ZUUL_REF | sed 's/^refs.tags.//'`
FILENAME_BIN="{name}-$TAG.jar"
# copy plugin artifacts from tarballs to local workspace
rm -rf *.jar
curl -o $FILENAME_BIN http://tarballs.openstack.org/ci/{name}/$FILENAME_BIN
# deploy to maven repository
FILENAME_POM="{name}-$TAG.pom"
/usr/local/jenkins/slave_scripts/mavencentral-upload.sh {name} $TAG \
$FILENAME_POM $FILENAME_BIN
publishers:
- console-log
- job-group:
name: maven-plugin-jobs
node:
- ubuntu-trusty
- ubuntu-xenial
jobs:
- 'gate-{name}-maven-build-{node}'
- '{name}-localrepo-upload-{node}'
- '{name}-mavencentral-upload'