From 3d4fb02986461d459f998d1e0198d9b0adc43686 Mon Sep 17 00:00:00 2001 From: Antoine Musso Date: Thu, 15 Nov 2012 13:27:42 +0100 Subject: [PATCH] jenkins user must have global read permission Change-Id: I467f2b8ca5fcffc118c1bdc3d5dee04c309ac70f Reviewed-on: https://review.openstack.org/16170 Reviewed-by: James E. Blair Approved: Jeremy Stanley Reviewed-by: Jeremy Stanley Tested-by: Jenkins --- doc/source/installation.rst | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/doc/source/installation.rst b/doc/source/installation.rst index 808282272..9b6170bd8 100644 --- a/doc/source/installation.rst +++ b/doc/source/installation.rst @@ -27,12 +27,14 @@ the following format:: url=JENKINS_URL **user** - This should be the name of a user previously defined in Jenkins with - the permissions necessary to read, create, delete, and configure - jobs. + This should be the name of a user previously defined in Jenkins. + 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 ``Create``, + ``Delete``, ``Configure`` and finally ``Read``. **password** - The API token for the user specified. You cat get this through the + The API token for the user specified. You can get this through the Jenkins management interface under ``People`` -> username -> ``Configure`` and then click the ``Show API Token`` button.