From 049c0306ca1b98a1afc371d56507b2620ab63f02 Mon Sep 17 00:00:00 2001 From: Anil Belur Date: Sat, 14 Jul 2018 19:55:03 +1000 Subject: [PATCH] Update Jenkins sandbox docs Update Jenkins sandbox docs with recommended options: * Add retain_anchors to config file * Add job only option Change-Id: If6d208e1e5b1b828615e34573b4f8f75b69e3178 Signed-off-by: Anil Belur --- docs/jenkins.rst | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/jenkins.rst b/docs/jenkins.rst index 25e5370f9..812f29b34 100644 --- a/docs/jenkins.rst +++ b/docs/jenkins.rst @@ -880,6 +880,9 @@ example is provided by releng/builder at `example-jenkins.ini`_. # Edit jenkins.ini with your username, API token and ODL's sandbox URL $ cat jenkins.ini + [job_builder] + retain_anchors=True + [jenkins] user= password= @@ -937,6 +940,9 @@ Once you've `configured your \`jenkins.ini\` `_ and `verified yo JJB jobs `_ produce valid XML descriptions of Jenkins jobs you can push them to the Jenkins sandbox. +Add the --jobs-only (-j) option to push only jobs to Jenkins sandbox. Pushing +views to Jenkins sandbox requires admin access. + .. important:: When pushing with `jenkins-jobs`, a log message with the number @@ -956,7 +962,7 @@ can push them to the Jenkins sandbox. .. code-block:: bash # Don't push all jobs by omitting the final param! (ctrl+c to abort) - jenkins-jobs --conf jenkins.ini update jjb/ + jenkins-jobs --conf jenkins.ini update -j 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 -- 2.36.6