zuul/zuul
Code Issues Proposed changes

document Jenkins user permissions

Browse Source 
This document the required permissions of the Zuul Jenkins user.

Change-Id: Id977e3813f943b032c7628d8cdc663b3bdbb688d
Reviewed-on: https://review.openstack.org/16528
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Approved: Clark Boylan <clark.boylan@gmail.com>
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Tested-by: Jenkins
This commit is contained in:
Antoine Musso 2012-11-20 15:07:07 +01:00 committed by Jenkins
parent 43cdeab65f
commit 2b2d2c40d5
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/source/launchers.rst
View File

@ -29,9 +29,13 @@ and then visit the configuration page for the user:
https://jenkins.example.com/user/USERNAME/configure
And click **Show API Token** to retrieve the API token for that user.
You will need this later when configuring Zuul. Make sure that this
user has appropriate permission to build any jobs that you want Zuul
to trigger.
You will need this later when configuring Zuul. Appropriate user
permissions must be set under the Jenkins security matrix: under the
``Global`` group of permissions, check ``Read``, then under the ``Job``
group of permissions, check ``Read`` and ``Build``. Finally, under
``Run`` check ``Update``. If using a per project matrix, make sure the
user permissions are properly set for any jobs that you want Zuul to
trigger.
Make sure the notification plugin is installed. Visit the plugin
manager on your jenkins: