ceph-csi/deploy/jjb-deploy.yaml
Niels de Vos 6a631e61cb ci: track jjb jobs by a jjb/session=<uuid> label
By using a template, it becomes possible to identify the Pod that has
been started by the Batch Job.

This prevents the script from getting the logs from an incorrect (old)
container.

Fixes: #1111
Signed-off-by: Niels de Vos <ndevos@redhat.com>
2020-05-29 09:51:16 +00:00

46 lines
1.1 KiB
YAML

---
kind: Template
apiVersion: v1
metadata:
name: my-template
objects:
- apiVersion: batch/v1
kind: Job
metadata:
labels:
app: jjb
jjb/session: "${SESSION}"
name: jjb-deploy
spec:
ttlSecondsAfterFinished: 0
backoffLimit: 1
template:
metadata:
labels:
app: jjb-deploy
jjb/session: "${SESSION}"
spec:
containers:
- name: jjb
image: 172.30.254.79:5000/ceph-csi/jjb:latest
env:
- name: GIT_REPO
value: https://github.com/ceph/ceph-csi
- name: GIT_REF
value: ci/centos
- name: MAKE_TARGET
value: deploy
volumeMounts:
- name: etc-jj
mountPath: /etc/jenkins_jobs
readOnly: true
volumes:
- name: etc-jj
configMap:
name: jenkins-jobs
restartPolicy: Never
parameters:
- name: SESSION
description: unique ID for the session to track the pod for the job
required: true