From c7298413114f6fb6596fec728e6d28f4853ad2ef Mon Sep 17 00:00:00 2001 From: Jamo Luhrsen Date: Tue, 17 Oct 2017 12:13:25 -0700 Subject: [PATCH] Add a snippet about using jjb-deploy keyword Change-Id: Ib67148cbf0b8f78ae22d25fa6a021eb5d6df0b99 Signed-off-by: Jamo Luhrsen --- docs/jenkins.rst | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/jenkins.rst b/docs/jenkins.rst index 40057f03b..ac10adcf2 100644 --- 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/ +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 + Running Jobs ^^^^^^^^^^^^ -- 2.36.6