-
Notifications
You must be signed in to change notification settings - Fork 20
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
Use PR workflow for updating the lockfile #32
Comments
related: we can open a PR via curl: |
Just mentioning this here for lack of a better place. Part of working on this, we should look at how we expect PR testing to work such that we can still get meaningful CI testing of overrides before merging. (See e.g. coreos/fedora-coreos-config#186 (comment)). |
I think one easy way to do this without having the tagger tag things in before merging is to have CI just go and fetch all the RPMs mentioned in the overrides directly from Koji and drop them in |
that's a good idea! |
I intend to use this to close the gap we have in upstream CI testing when adding overrides: coreos#32 (comment)
I intend to use this to close the gap we have in upstream CI testing when adding overrides: coreos#32 (comment)
This is obsolete now that we've moved lockfile bumping to https://github.com/coreos/fedora-coreos-pipeline/blob/main/jobs/bump-lockfile.Jenkinsfile. |
Right now,
config-bot
only supports directly promoting the lockfile usinggit push
. We should enhance it so that it instead opens up a PR to bump the lockfile. This unlocks (pun intended) a few things:testing-devel
would be unbuildable. Switching to a PR workflow would allow e.g. a merge bot to do the tagging and waiting for the repo respin before doing the merge, so thattesting-devel
can always be built.The text was updated successfully, but these errors were encountered: