Remove zmq-event-publisher jobs

These jobs are not used anymore, remove them.

Depends-On: https://review.opendev.org/702745
Change-Id: I1c6447f9997e953d3f0a0030b46bd910e8910e0c
This commit is contained in:
Andreas Jaeger 2020-01-15 21:27:30 +01:00
parent f50df68362
commit d1e5be8c71
5 changed files with 0 additions and 203 deletions

View File

@ -1,21 +0,0 @@
- hosts: primary
tasks:
- name: Ensure artifacts directory exists
file:
path: '{{ zuul.executor.work_root }}/artifacts'
state: directory
delegate_to: localhost
- name: Copy files from {{ ansible_user_dir }}/workspace/ on node
synchronize:
src: '{{ ansible_user_dir }}/workspace/'
dest: '{{ zuul.executor.work_root }}/artifacts/$ZUUL_SHORT_PROJECT_NAME'
mode: pull
copy_links: true
verify_host: true
rsync_opts:
- --include=/target/$ZUUL_SHORT_PROJECT_NAME-*.hpi
- --include=*/
- --exclude=*
- --prune-empty-dirs

View File

@ -1,62 +0,0 @@
- hosts: all
name: Autoconverted job legacy-zmq-event-publisher-hpi-artifact from old job zmq-event-publisher-hpi-artifact
roles:
- bindep
tasks:
- name: Ensure legacy workspace directory
file:
path: '{{ ansible_user_dir }}/workspace'
state: directory
- shell:
cmd: |
set -e
set -x
CLONEMAP=`mktemp`
function cleanup {
# In cases where zuul-cloner is aborted during a git
# clone operation, git will remove the git work tree in
# its cleanup. The work tree in these jobs is the
# workspace directory, which means that subsequent
# jenkins post-build actions can not run because the
# workspace has been removed.
# To reduce the likelihood of this having an impact,
# recreate the workspace directory if needed
mkdir -p $WORKSPACE
rm -f $CLONEMAP
}
trap cleanup EXIT
cat > $CLONEMAP << EOF
clonemap:
- name: $ZUUL_PROJECT
dest: .
EOF
/usr/zuul-env/bin/zuul-cloner -m $CLONEMAP --cache-dir /opt/git \
https://opendev.org $ZUUL_PROJECT
executable: /bin/bash
chdir: '{{ ansible_user_dir }}/workspace'
environment: '{{ zuul | zuul_legacy_vars }}'
- shell:
cmd: |
set -x
sudo rm -f /etc/sudoers.d/zuul
# Prove that general sudo access is actually revoked
! sudo -n true
executable: /bin/bash
chdir: '{{ ansible_user_dir }}/workspace'
environment: '{{ zuul | zuul_legacy_vars }}'
- shell:
cmd: |
set -e
set -x
/usr/local/jenkins/slave_scripts/version-properties.sh
source version.properties
mvn clean package -B -Dproject-version=$PROJECT_VER
cp ./target/$ZUUL_SHORT_PROJECT_NAME.hpi ./target/$ZUUL_SHORT_PROJECT_NAME-$PROJECT_VER.hpi
executable: /bin/bash
chdir: '{{ ansible_user_dir }}/workspace'
environment: '{{ zuul | zuul_legacy_vars }}'

View File

@ -1,38 +0,0 @@
- hosts: all
name: Autoconverted job legacy-zmq-event-publisher-jenkinsci-upload from old job
zmq-event-publisher-jenkinsci-upload
tasks:
- name: Ensure legacy workspace directory
file:
path: '{{ ansible_user_dir }}/workspace'
state: directory
- shell:
cmd: |
set -x
sudo rm -f /etc/sudoers.d/zuul
# Prove that general sudo access is actually revoked
! sudo -n true
executable: /bin/bash
chdir: '{{ ansible_user_dir }}/workspace'
environment: '{{ zuul | zuul_legacy_vars }}'
- shell:
cmd: |
set -e
set -x
TAG=`echo $ZUUL_REF | sed 's/^refs.tags.//'`
FILENAME_HPI="$ZUUL_SHORT_PROJECT_NAME-$TAG.hpi"
# copy plugin artifacts from tarballs to local workspace
rm -rf *.hpi
curl -o $FILENAME_HPI http://tarballs.openstack.org/ci/$ZUUL_SHORT_PROJECT_NAME/$FILENAME_HPI
# deploy to maven repository
FILENAME_POM="$ZUUL_SHORT_PROJECT_NAME-$TAG.pom"
/usr/local/jenkins/slave_scripts/jenkinsci-upload.sh $ZUUL_SHORT_PROJECT_NAME $TAG \
$FILENAME_POM $FILENAME_HPI
executable: /bin/bash
chdir: '{{ ansible_user_dir }}/workspace'
environment: '{{ zuul | zuul_legacy_vars }}'

View File

@ -1,62 +0,0 @@
- hosts: all
name: Autoconverted job legacy-zmq-event-publisher-maven-build-ubuntu-trusty from
old job gate-zmq-event-publisher-maven-build-ubuntu-trusty
roles:
- bindep
tasks:
- name: Ensure legacy workspace directory
file:
path: '{{ ansible_user_dir }}/workspace'
state: directory
- shell:
cmd: |
set -e
set -x
CLONEMAP=`mktemp`
function cleanup {
# In cases where zuul-cloner is aborted during a git
# clone operation, git will remove the git work tree in
# its cleanup. The work tree in these jobs is the
# workspace directory, which means that subsequent
# jenkins post-build actions can not run because the
# workspace has been removed.
# To reduce the likelihood of this having an impact,
# recreate the workspace directory if needed
mkdir -p $WORKSPACE
rm -f $CLONEMAP
}
trap cleanup EXIT
cat > $CLONEMAP << EOF
clonemap:
- name: $ZUUL_PROJECT
dest: .
EOF
/usr/zuul-env/bin/zuul-cloner -m $CLONEMAP --cache-dir /opt/git \
https://opendev.org $ZUUL_PROJECT
executable: /bin/bash
chdir: '{{ ansible_user_dir }}/workspace'
environment: '{{ zuul | zuul_legacy_vars }}'
- shell:
cmd: |
set -x
sudo rm -f /etc/sudoers.d/zuul
# Prove that general sudo access is actually revoked
! sudo -n true
executable: /bin/bash
chdir: '{{ ansible_user_dir }}/workspace'
environment: '{{ zuul | zuul_legacy_vars }}'
- shell:
cmd: |
set -e
set -x
/usr/local/jenkins/slave_scripts/version-properties.sh
source version.properties
mvn clean package -B -Dproject-version=$PROJECT_VER
executable: /bin/bash
chdir: '{{ ansible_user_dir }}/workspace'
environment: '{{ zuul | zuul_legacy_vars }}'

View File

@ -1186,23 +1186,3 @@
required-projects:
- openstack/devstack-gate
- x/trio2o
- job:
name: legacy-zmq-event-publisher-hpi-artifact
parent: legacy-publish-openstack-artifacts
run: playbooks/legacy/zmq-event-publisher-hpi-artifact/run.yaml
post-run: playbooks/legacy/zmq-event-publisher-hpi-artifact/post.yaml
timeout: 1800
- job:
name: legacy-zmq-event-publisher-jenkinsci-upload
parent: legacy-base
run: playbooks/legacy/zmq-event-publisher-jenkinsci-upload/run.yaml
timeout: 1800
- job:
name: legacy-zmq-event-publisher-maven-build-ubuntu-trusty
parent: legacy-base
run: playbooks/legacy/zmq-event-publisher-maven-build-ubuntu-trusty/run.yaml
timeout: 1800
nodeset: legacy-ubuntu-trusty