From 70a22bad1af960642b2452339758ececff9706c3 Mon Sep 17 00:00:00 2001 From: Jamo Luhrsen Date: Tue, 17 Oct 2017 12:08:22 -0700 Subject: [PATCH 1/1] Add a snippet about using jjb-deploy keyword Change-Id: Ia3c1a602a7c629943c906ca3bbb57152bd66e98c Signed-off-by: Jamo Luhrsen --- docs/system-test-guide.rst | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/docs/system-test-guide.rst b/docs/system-test-guide.rst index 48341fad10..e76d64adde 100644 --- a/docs/system-test-guide.rst +++ b/docs/system-test-guide.rst @@ -357,9 +357,18 @@ Before pushing your system test job into jenkins-releng_, it is recommended to debug the job as well as the you system test code in the sandbox. To do that: * Set up sandbox access using jenkins-sandbox-install_ instruction. -* Push you new csit job to sandbox:: +* Push your new csit job to sandbox: - jenkins-jobs --conf jenkins.ini update jjb/ $project-csit-1node-$functionality-only-$branch + Method 1: + + you can write a comment in a releng/builder gerrit patch to have the job automatically created + in the sandbox. The format of the comment is:: + + jjb-deploy + + Method 2:: + + jenkins-jobs --conf jenkins.ini update jjb/ $project-csit-1node-$functionality-only-$branch * Open your job in jenkins-sandbox_ and start a build replacing the PATCHREFSPEC parameter by your int/test patch REFSPEC (e.g. refs/changes/85/23185/1). you -- 2.36.6