Create tool for propagating changes from testing-devel to bodhi-updates #204
Comments
8 tasks
|
Yeah I was actually thinking about this on Friday. It's almost like we want "everything else, but two files". We need overlayfs for our git repos now 😄 |
jlebon
added a commit
to jlebon/fedora-coreos-config
that referenced
this issue
Jul 5, 2019
This is prep for having `testing-devel` be the source of truth for all the files other than the lockfile and manifest (see [1]). We just have one `fedora.repo` file which contains all the repos we care about, but only actually enable the appropriate ones for each stream independently. In this case, once packages are tagged, `testing-devel` will just use the `coreos-pool` repo. [1] coreos/fedora-coreos-tracker#204
jlebon
added a commit
to coreos/fedora-coreos-config
that referenced
this issue
Jul 5, 2019
This is prep for having `testing-devel` be the source of truth for all the files other than the lockfile and manifest (see [1]). We just have one `fedora.repo` file which contains all the repos we care about, but only actually enable the appropriate ones for each stream independently. In this case, once packages are tagged, `testing-devel` will just use the `coreos-pool` repo. [1] coreos/fedora-coreos-tracker#204
|
Anything left for this? |
|
Nope, done! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our main development stream is
testing-devel(e.g. it's the default branch for https://github.com/coreos/fedora-coreos-config). But we want changes we commit to it (e.g. changes tooverlay/) to propagate automatically intobodhi-updates. Basically, the only differences betweenbodhi-updatesandtesting-develshould be (1) lockfiles/overrides intesting-devel, and (2)manifest.yaml(which holds the stream-specific ref and repos).So we need a tool that will automatically merge changes to everything else from
testing-develtobodhi-updates(and then in the futurebodhi-updates-testingas well).The text was updated successfully, but these errors were encountered: