Skip to content
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

Closed
jlebon opened this issue Aug 19, 2019 · 5 comments
Closed

Use PR workflow for updating the lockfile #32

jlebon opened this issue Aug 19, 2019 · 5 comments

Comments

@jlebon
Copy link
Member

jlebon commented Aug 19, 2019

Right now, config-bot only supports directly promoting the lockfile using git push. We should enhance it so that it instead opens up a PR to bump the lockfile. This unlocks (pun intended) a few things:

  • a better CI workflow: we can actually test the OS against the latest base content before absorbing it
  • smarter integration with coreos-koji-tagger: right now, it tags packages once the lockfile is merged, at which point builds won't actually succeed until the packages are signed (if not already), moved to the coreos-pool tag, and the coreos-pool repo is respinned. This means that there's a window of time during which 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 that testing-devel can always be built.
@dustymabe
Copy link
Member

related: we can open a PR via curl:

https://github.com/coreos/fedora-coreos-pipeline/blob/cf9f40ede1ac700074ade168d383f68529ad4fff/Jenkinsfile.stream.metadata.generator#L59

@jlebon
Copy link
Member Author

jlebon commented Sep 26, 2019

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)).

@jlebon
Copy link
Member Author

jlebon commented Oct 11, 2019

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 before merging.

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 overrides/rpm.

@dustymabe
Copy link
Member

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 overrides/rpm.

that's a good idea!

jlebon added a commit to jlebon/fedora-coreos-releng-automation that referenced this issue Dec 9, 2019
I intend to use this to close the gap we have in upstream CI testing
when adding overrides:

coreos#32 (comment)
jlebon added a commit to jlebon/fedora-coreos-releng-automation that referenced this issue Dec 9, 2019
I intend to use this to close the gap we have in upstream CI testing
when adding overrides:

coreos#32 (comment)
@jlebon
Copy link
Member Author

jlebon commented Apr 26, 2022

This is obsolete now that we've moved lockfile bumping to https://github.com/coreos/fedora-coreos-pipeline/blob/main/jobs/bump-lockfile.Jenkinsfile.

@jlebon jlebon closed this as completed Apr 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants