diff --git a/docs/configuration/downstream/bodhi_update.md b/docs/configuration/downstream/bodhi_update.md index 2335be0b3b..abfa766c82 100644 --- a/docs/configuration/downstream/bodhi_update.md +++ b/docs/configuration/downstream/bodhi_update.md @@ -5,6 +5,8 @@ sidebar_position: 3 # `job: bodhi_update` +![Bodhi updates](../../img/configuration/bodhi-updates.png) + Create a new update in [Fedora Bodhi](https://bodhi.fedoraproject.org) for successful Koji build. diff --git a/docs/configuration/downstream/koji_build.md b/docs/configuration/downstream/koji_build.md index 934d1d9c7b..ebe28e886d 100644 --- a/docs/configuration/downstream/koji_build.md +++ b/docs/configuration/downstream/koji_build.md @@ -5,6 +5,8 @@ sidebar_position: 2 # `job: koji_build` +![Koji build](../../img/configuration/koji-info.png) + Trigger the build in [Fedora Koji](https://koji.fedoraproject.org/koji/) build system as a reaction to a new dist-git commit. diff --git a/docs/configuration/upstream/copr_build.md b/docs/configuration/upstream/copr_build.md index 3b134d97c7..356909a82b 100644 --- a/docs/configuration/upstream/copr_build.md +++ b/docs/configuration/upstream/copr_build.md @@ -5,6 +5,8 @@ sidebar_position: 1 # `job: copr_build` +![Copr build](../../img/configuration/copr-overview.png) + Create an SRPM and submit an RPM build to [Fedora Copr](https://copr.fedorainfracloud.org/) build system. diff --git a/docs/fedora-releases-guide/index.md b/docs/fedora-releases-guide/index.md index 7f6e06ec86..a8bfc951e0 100644 --- a/docs/fedora-releases-guide/index.md +++ b/docs/fedora-releases-guide/index.md @@ -11,6 +11,8 @@ Let's split the release process into single steps: 4. [Koji builds](#koji-build-job) 5. [Bodhi updates](#bodhi-update-job) +![Release steps](../img/fedora-releases-guide/release-steps.png) + Doing Fedora releases with Packit means utilising these jobs: 1. [`propose_downstream` or `pull_from_upstream`](#propose-downstream-or-pull-from-upstream) 2. [`koji_build`](#koji-build-job) @@ -18,6 +20,8 @@ Doing Fedora releases with Packit means utilising these jobs: Every job takes care of a different part of the release process. +![Packit flow chart](../img/fedora-releases-guide/process-diagram.png) + :::tip In this page, you can find all the details of the release process automation covered by Packit. @@ -233,6 +237,8 @@ By default, only merged pull requests created by Packit are being acted upon, bu you can override this behaviour by specifying `allowed_pr_authors` and/or `allowed_committers` in the [job configuration](/docs/configuration/downstream/koji_build). +![Koji build](../img/fedora-releases-guide/koji-build.png) + For a configuration example and retriggering, see [dist-git onboarding](./dist-git-onboarding.md#koji-build-job). ## Bodhi update job @@ -246,6 +252,8 @@ By default, only successful Koji builds created by Packit are being acted upon, you can override this behaviour by specifying `allowed_builders` in the [job configuration](/docs/configuration/downstream/bodhi_update). +![Bodhi updates](../img/fedora-releases-guide/bodhi-updates.png) + For a configuration example and retriggering, see [dist-git onboarding](./dist-git-onboarding.md#bodhi-update-job). diff --git a/docs/fedora-releases-guide/non-divergent-dist-git-branches.md b/docs/fedora-releases-guide/non-divergent-dist-git-branches.md index 3ae1d9e85d..9404bfbf94 100644 --- a/docs/fedora-releases-guide/non-divergent-dist-git-branches.md +++ b/docs/fedora-releases-guide/non-divergent-dist-git-branches.md @@ -5,6 +5,8 @@ sidebar_position: 7 # Non-divergent dist-git branches +![Branches](../img/fedora-releases-guide/non-divergent-branches.png) + To prevent your dist-git branches from diverging, you can use the following `dist_git_branches` syntax: ```yaml diff --git a/docs/img/configuration/bodhi-updates.png b/docs/img/configuration/bodhi-updates.png new file mode 100644 index 0000000000..8d1966734c Binary files /dev/null and b/docs/img/configuration/bodhi-updates.png differ diff --git a/docs/img/configuration/copr-overview.png b/docs/img/configuration/copr-overview.png new file mode 100644 index 0000000000..96a51c648c Binary files /dev/null and b/docs/img/configuration/copr-overview.png differ diff --git a/docs/img/configuration/koji-info.png b/docs/img/configuration/koji-info.png new file mode 100644 index 0000000000..2856d325ae Binary files /dev/null and b/docs/img/configuration/koji-info.png differ diff --git a/docs/img/fedora-releases-guide/bodhi-updates.png b/docs/img/fedora-releases-guide/bodhi-updates.png new file mode 100644 index 0000000000..1740f8b229 Binary files /dev/null and b/docs/img/fedora-releases-guide/bodhi-updates.png differ diff --git a/docs/img/fedora-releases-guide/koji-build.png b/docs/img/fedora-releases-guide/koji-build.png new file mode 100644 index 0000000000..2e383d27fa Binary files /dev/null and b/docs/img/fedora-releases-guide/koji-build.png differ diff --git a/docs/img/fedora-releases-guide/non-divergent-branches.png b/docs/img/fedora-releases-guide/non-divergent-branches.png new file mode 100644 index 0000000000..49d26858d1 Binary files /dev/null and b/docs/img/fedora-releases-guide/non-divergent-branches.png differ diff --git a/docs/img/fedora-releases-guide/process-diagram.png b/docs/img/fedora-releases-guide/process-diagram.png new file mode 100644 index 0000000000..dba1fa6cd5 Binary files /dev/null and b/docs/img/fedora-releases-guide/process-diagram.png differ diff --git a/docs/img/fedora-releases-guide/release-steps.png b/docs/img/fedora-releases-guide/release-steps.png new file mode 100644 index 0000000000..692623c12b Binary files /dev/null and b/docs/img/fedora-releases-guide/release-steps.png differ diff --git a/docs/img/retriggering/comment.png b/docs/img/retriggering/comment.png new file mode 100644 index 0000000000..ccbb29daf8 Binary files /dev/null and b/docs/img/retriggering/comment.png differ diff --git a/docs/retriggering.md b/docs/retriggering.md index 013c73fd6c..0b6d9962aa 100644 --- a/docs/retriggering.md +++ b/docs/retriggering.md @@ -7,6 +7,8 @@ sidebar_position: 7 In general, you can put a `/packit ` comment to trigger the Packit job manually. +![Re-run GitHub check](img/retriggering/comment.png) + ### copr_build For retriggering the [`copr_build`](/docs/configuration/upstream/copr_build) jobs, Packit is able to trigger new builds based on a pull request comment: