Log $JOB_NAME with the jjb-deploy 48/16348/3
authorAnil Belur <abelur@linuxfoundation.org>
Mon, 29 Jul 2019 01:33:00 +0000 (11:33 +1000)
committerAnil Belur <abelur@linuxfoundation.org>
Wed, 31 Jul 2019 22:07:30 +0000 (08:07 +1000)
Change-Id: Ifb2715402dc1dcb21708e4dc8851e0c621d59145
Signed-off-by: Anil Belur <abelur@linuxfoundation.org>
releasenotes/notes/add-job-name-in-logs-9c993fa59310d9c7.yaml [new file with mode: 0644]
shell/jjb-deploy-job.sh

diff --git a/releasenotes/notes/add-job-name-in-logs-9c993fa59310d9c7.yaml b/releasenotes/notes/add-job-name-in-logs-9c993fa59310d9c7.yaml
new file mode 100644 (file)
index 0000000..66536cd
--- /dev/null
@@ -0,0 +1,6 @@
+---
+fixes:
+  - |
+    There is no way on finding out the $JOB_NAME pushed to sandbox with the
+    jjb-deploy command in the logs. The change outputs the $JOB_NAME to the
+    logs, which is useful for debugging purposes.
index 99ef367..5efb9f4 100644 (file)
@@ -35,4 +35,5 @@ if [ -z "${JOB_NAME//\*/}" ]; then
     exit 1
 fi
 
+echo "Deploying Job $JOB_NAME to sandbox"
 jenkins-jobs -s sandbox update --jobs-only --recursive --workers 4 jjb/ "$JOB_NAME"