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>

deploy/jjb-validate.yaml

@@ -1,23 +1,35 @@
 ---
-apiVersion: batch/v1
-kind: Job
+kind: Template
+apiVersion: v1
 metadata:
-  labels:
-    app: jjb-validate
   name: jjb-validate
-spec:
-  ttlSecondsAfterFinished: 0
-  backoffLimit: 1
-  template:
-    labels:
-      app: jjb-validate
+objects:
+  - apiVersion: batch/v1
+    kind: Job
+    metadata:
+      labels:
+        app: jjb-validate
+        jjb/session: "${SESSION}"
+      name: jjb-validate
     spec:
-      containers:
-        - name: jjb-validate
-          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
-      restartPolicy: Never
+      ttlSecondsAfterFinished: 0
+      backoffLimit: 1
+      template:
+        metadata:
+          labels:
+            app: jjb-validate
+            jjb/session: "${SESSION}"
+        spec:
+          containers:
+            - name: jjb-validate
+              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
+          restartPolicy: Never
+parameters:
+  - name: SESSION
+    description: unique ID for the session to track the pod for the job
+    required: true