-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add more docs on permissions in downstream jobs #851
Add more docs on permissions in downstream jobs #851
Conversation
Build succeeded. ✔️ pre-commit SUCCESS in 1m 20s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks Maja, really nicelly written, just few comments
|
||
Packit provides an overview of its own updates [here](https://dashboard.packit.dev/jobs/bodhi-updates). | ||
|
||
You can also utilise |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for updating this!
Build succeeded. ✔️ pre-commit SUCCESS in 1m 21s |
4a79d42
to
2f3ccb2
Compare
Build succeeded. ✔️ pre-commit SUCCESS in 1m 19s |
docs/fedora-releases-guide/index.md
Outdated
|
||
# Permission Handling | ||
|
||
The downstream automation is a chain of jobs: propose downstream/pull from upstream -> koji build -> bodhi update. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The downstream automation is a chain of jobs: propose downstream/pull from upstream -> koji build -> bodhi update. | |
The downstream automation is a pipeline of jobs: propose_downstream/pull_from_upstream -> koji_build -> bodhi_update. |
Technically, the first part is optional, one can start a pipeline with a direct push. Should we mention that somehow?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about something like this:
The downstream automation is a chain of jobs: propose downstream/pull from upstream -> koji build -> bodhi update. | |
The downstream automation is a pipeline of jobs: propose_downstream/pull_from_upstream/your-own commits -> koji_build -> bodhi_update. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But it could also be Packit commits pushed by a user 🙂
Actually, it should look more like this:
propose_downstream/pull_from_upstream -> Packit PR merge/dist-git push -> koji_build -> bodhi_update.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or perhaps this is more accurate:
propose_downstream/pull_from_upstream -> Packit PR merge -> koji_build -> bodhi_update
PR merge/dist-git push -> koji_build -> bodhi_update
Build succeeded. ✔️ pre-commit SUCCESS in 1m 12s |
Build succeeded. ✔️ pre-commit SUCCESS in 1m 14s |
Co-authored-by: Laura Barcziová <49026743+lbarcziova@users.noreply.github.com> Co-authored-by: Nikola Forró <nforro@redhat.com>
647e75e
to
4cbea3f
Compare
Build succeeded. ✔️ pre-commit SUCCESS in 1m 23s |
Build succeeded. ✔️ pre-commit SUCCESS in 1m 11s |
Build succeeded. ✔️ pre-commit SUCCESS in 1m 13s |
Co-authored-by: Nikola Forró <nforro@redhat.com>
4f26fc9
to
76bb0ba
Compare
Build succeeded. ✔️ pre-commit SUCCESS in 1m 17s |
No description provided.