From 0cd8e1fb4060a3a34ea9dd08ceacab7317d7cba9 Mon Sep 17 00:00:00 2001 From: Michal Konečný Date: Nov 29 2022 14:48:54 +0000 Subject: Update pagure CI guide I noticed that the notification from post build is not sent to PR and after some investigation I found out that the credentials need to contain CI token instead of API key. Unfortunately you can't look at the secret text in Jenkins configuration, so it took some time till I was able to figure this out. Signed-off-by: Michal Konečný --- diff --git a/doc/usage/pagure_ci_jenkins.rst b/doc/usage/pagure_ci_jenkins.rst index fef429b..14072a0 100644 --- a/doc/usage/pagure_ci_jenkins.rst +++ b/doc/usage/pagure_ci_jenkins.rst @@ -122,9 +122,9 @@ Example Script # Part of the script specific to how you run the tests on your project -* To use the URL to POST results you need to add API key to Jenkins instance. - This API key needs to have `Update an issue, status, comments, custom fields...` - ACL. In Jenkins add it in `Manage Jenkins` -> `Manage Credentials` -> `Stores scoped to Jenkins` +* To use the URL to POST results you need to add CI token to Jenkins instance. + This token could be found in Pagure project `Settings` -> `Hooks` -> `Pagure CI`. + In Jenkins add it in `Manage Jenkins` -> `Manage Credentials` -> `Stores scoped to Jenkins` -> `Jenkins` -> `Global credentials (unrestricted)` -> `Add Credentials` as kind `Secret text` (ID will be used in script).