schema: support multiple images destinations#4038
Conversation
in coreos/fedora-coreos-pipeline#1091 we started publishing container images in multiples repos. However the build.json was not reflecting that, only storing the last pushed image data, overwriting it with each arch. See coreos#4038 See coreos/fedora-coreos-pipeline#1099
in coreos/fedora-coreos-pipeline#1091 we started publishing container images in multiples repos. However the build.json was not reflecting that, only storing the last pushed image data, overwriting it with each arch. See coreos#4038 See coreos/fedora-coreos-pipeline#1099
037b948 to
6a620fb
Compare
|
Ok just tested that, pushing a couple of manifests on a testing repo : |
in coreos/fedora-coreos-pipeline#1091 we started publishing container images in multiples repos. However the build.json was not reflecting that, only storing the last pushed image data, overwriting it with each arch. See coreos#4038 See coreos/fedora-coreos-pipeline#1099
6a620fb to
69262ba
Compare
in coreos/fedora-coreos-pipeline#1091 we started publishing container images in multiples repos. However the build.json was not reflecting that, only storing the last pushed image data, overwriting it with each arch. See coreos#4038 See coreos/fedora-coreos-pipeline#1099
69262ba to
7b93e72
Compare
jlebon
left a comment
There was a problem hiding this comment.
Needs a make schema-update. LGTM otherwise!
in coreos/fedora-coreos-pipeline#1091 we started publishing container images in multiples repos. However the build.json was not reflecting that, only storing the last pushed image data, overwriting it with each arch. See coreos#4038 See coreos/fedora-coreos-pipeline#1099
7b93e72 to
ca4beba
Compare
in coreos/fedora-coreos-pipeline#1091 we started publishing container images in multiples repos. However the build.json was not reflecting that, only storing the last pushed image data, overwriting it with each arch. See coreos#4038 See coreos/fedora-coreos-pipeline#1099
ca4beba to
d99eb2f
Compare
i am hitting #4043 |
ravanelli
left a comment
There was a problem hiding this comment.
I would change the commit message:
Note that I had to force the update for entries in `go.sum` as the checksums had
changed. Fixes https://github.com/coreos/coreos-assembler/issues/4043.
257809d to
b33dc1f
Compare
in coreos/fedora-coreos-pipeline#1091 we started publishing container images in multiples repos. However the build.json was not reflecting that, only storing the last pushed image data, overwriting it with each arch. See coreos#4038 See coreos/fedora-coreos-pipeline#1099
e173c7d to
c61bd56
Compare
in coreos/fedora-coreos-pipeline#1091 we started publishing container images in multiples repos. However the build.json was not reflecting that, only storing the last pushed image data, overwriting it with each arch. See coreos#4038 See coreos/fedora-coreos-pipeline#1099
c61bd56 to
117ba69
Compare
|
The test failure have nothing to do with this change /override ci/prow/rhcos |
|
@jbtrystram: Overrode contexts on behalf of jbtrystram: ci/prow/rhcos DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
jlebon
left a comment
There was a problem hiding this comment.
You should be able to test the GC parts using --dry-run.
in coreos/fedora-coreos-pipeline#1091 we started publishing container images in multiples repos. However the build.json was not reflecting that, only storing the last pushed image data, overwriting it with each arch. See coreos#4038 See coreos/fedora-coreos-pipeline#1099
117ba69 to
4c900b8
Compare
|
I just duplicated the quay image in the latest rawhide |
b88df6c to
54813ce
Compare
In coreos/fedora-coreos-pipeline#1091 we added the possibility of publishing container images to multiples repositories. This needs to be reflected in the schema otherwhise we only record one image (currenlty the last pushed). Add a `primary-image` key that extends image by adding an `additional-images` array. Use that for relevant container images objects. See coreos/fedora-coreos-pipeline#1099
in coreos/fedora-coreos-pipeline#1091 we started publishing container images in multiples repos. However the build.json was not reflecting that, only storing the last pushed image data, overwriting it with each arch. See coreos#4038 See coreos/fedora-coreos-pipeline#1099
In fb222e2 we introduced additionnal images in the schema, update the generated go code to match.
54813ce to
1e8ac91
Compare
|
/retest |
|
Prow CI failure here is unrelated. /override ci/prow/rhcos |
|
@jlebon: Overrode contexts on behalf of jlebon: ci/prow/rhcos DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
in coreos/fedora-coreos-pipeline#1091 we started publishing container images in multiples repos. However the build.json was not reflecting that, only storing the last pushed image data, overwriting it with each arch. See #4038 See coreos/fedora-coreos-pipeline#1099
In coreos/fedora-coreos-pipeline#1091 we added the possibility of publishing container images to multiples repositories.
This needs to be reflected in the schema otherwhise we only record one image (currenlty the last pushed).
Add a
primary-imagekey that extends image by adding anadditional-imagesarray.Use that for relevant container images objects.
See coreos/fedora-coreos-pipeline#1099