summary |
shortlog |
log |
commit | commitdiff |
review |
tree
raw |
patch |
inline | side by side (from parent 1:
9260a94)
Change-Id: Ia3c1a602a7c629943c906ca3bbb57152bd66e98c
Signed-off-by: Jamo Luhrsen <jluhrsen@redhat.com>
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.
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 <job name>
+
+ 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
* 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