From bb3b7357fb48663931dae21f054eca8476c0ab3b Mon Sep 17 00:00:00 2001 From: Maja Massarini Date: Fri, 2 Dec 2022 14:12:59 +0100 Subject: [PATCH 1/2] Docs for retriggering through issue comment Co-authored-by: Jiri Popelka Co-authored-by: Tomas Tomecek --- content/docs/Configuration/_index.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/content/docs/Configuration/_index.md b/content/docs/Configuration/_index.md index 2fff52662a..81f817bc7f 100644 --- a/content/docs/Configuration/_index.md +++ b/content/docs/Configuration/_index.md @@ -336,6 +336,13 @@ By default, no issue will be created so Packit doesn't unintentionally spam any By enabling this setting, Packit will either create a new issue or add a comment to an already existing issue. In that case, the issue will be reused and a new comment will be added. +When a downstream job fails (Koji build or Bodhi update), +you can re-trigger the failed job through a comment like +`/packit koji-build` or `/packit create-update` in the opened issue. +The Packit app has to be installed in the issue repository and the +user, which commented, needs to have write permissions +into the repository in order for the retriggering to work. + #### copy_upstream_release_description (*bool*) When doing a new update in Fedora dist-git, the [GitHub upstream release description](https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases) From 36fa90ad2c2a21c7dc900049a0992d61528a9ad1 Mon Sep 17 00:00:00 2001 From: Maja Massarini Date: Fri, 16 Dec 2022 09:41:44 +0100 Subject: [PATCH 2/2] User profile should be accessible, update docs MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: František Nečas --- content/docs/Configuration/_index.md | 4 ++-- content/docs/guide.md | 7 +++++++ 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a/content/docs/Configuration/_index.md b/content/docs/Configuration/_index.md index 81f817bc7f..4a08ac38e5 100644 --- a/content/docs/Configuration/_index.md +++ b/content/docs/Configuration/_index.md @@ -336,11 +336,11 @@ By default, no issue will be created so Packit doesn't unintentionally spam any By enabling this setting, Packit will either create a new issue or add a comment to an already existing issue. In that case, the issue will be reused and a new comment will be added. -When a downstream job fails (Koji build or Bodhi update), +When a downstream job (e.g. Koji build or Bodhi update) fails, you can re-trigger the failed job through a comment like `/packit koji-build` or `/packit create-update` in the opened issue. The Packit app has to be installed in the issue repository and the -user, which commented, needs to have write permissions +user, who commented, needs to have write permissions into the repository in order for the retriggering to work. #### copy_upstream_release_description diff --git a/content/docs/guide.md b/content/docs/guide.md index 9a73d6e14e..31f56bda85 100644 --- a/content/docs/guide.md +++ b/content/docs/guide.md @@ -298,6 +298,13 @@ or are run in a particular step as a hook (with no action run by default). Take a look at the tables [here](/docs/actions/) to know what actions are available for each job. +### Users + +Packit checks if the user has sufficient permissions to complete a job (this depends on the job type). +For this reason the profile of a Packit user has to be accessible. +For example, on Github this means that the membership of a user to their team has to be public (see https://github.com/orgs/[org_name]/people/[user_name] ). + + ### How to try that for real In order to start using Packit, we suggest you [install the tooling locally](/docs/cli/#installation). All