Github action example with bodhi: https://github.com/fedora-infra/bodhi/blob/develop/.github/workflows/staging.yml

Packit can be used for both package building and update release (it will create and update in bodhi).

We could have a CI job that will build and push an update to Bodhi in each tag release/commit/whatever trigger we want to set.

Packit also allow us to easily run it locally to test CI jobs and it can integrate with different platforms such as Koji, COPR, etc.

We may need bot accounts for both Bodhi and Koji.

Sample packit command for copr: packit -d copr-build --project foobar --targets fedora-35-x86_6

Bonus: looks like we even leverage packit CI service: https://packit.dev/docs/packit-service/#easy-to-use

That not supported in pagure but it is in both github and gitlab, there is an open issue about pagure support: https://github.com/packit/packit-service/issues/556

Pagure reposiries would need a third-party CI service, such as jenkins, to invoke the packit cli to trigger builds/updates.

Sample: https://github.com/fedora-infra/the-new-hotness/pull/432