Add a snippet about using jjb-deploy keyword

Change-Id: Ib67148cbf0b8f78ae22d25fa6a021eb5d6df0b99
Signed-off-by: Jamo Luhrsen <jluhrsen@redhat.com>

diff --git a/docs/jenkins.rst b/docs/jenkins.rst
index 40057f03b9e2b3d31dc6dc648b157731515628ef..ac10adcf2323386c52acc19a8b114be257fdb177 100644 (file)
--- a/docs/jenkins.rst
+++ b/docs/jenkins.rst
@@ -863,6 +863,13 @@ can push them to the Jenkins sandbox.
         # Don't push all jobs by omitting the final param! (ctrl+c to abort)
         jenkins-jobs --conf jenkins.ini update jjb/ <job-name>
 
+Alternatively, you can push a job to the Jenkins sandbox with a special comment in a
+releng/builder gerrit patch. The job will be based off of the code your patch is
+based upon. Meaning, if your patch is changing something related to the job you are
+pushing, those changes will exist in the sandbox job. The format of the comment is::
+
+        jjb-deploy <job name>
+
 Running Jobs
 ^^^^^^^^^^^^