Parent build id from candidate registry
Opened this issue · 5 comments
Hello.
I'm sorry if this question does not belong here but this project is the closest point to my problem I've found. Basically, the question is: is it somehow possible to tell atomic-reactor to look for a parent image also on candidate-registry.fedoraproject.org?
I maintain this chain of container images: s2i-core -> s2i-base -> python3 and it would be nice to have a possibility to build all of them at once and then create a single update for all of them. Currently, I have to build s2i-core, wait until it goes through the update process, then build s2i-base, wait for the update to finish, and then the same for python3. If I don't get karma from users, this procedure might take weeks.
Ideally, I'd need to build s2i-core, s2i-base on top of the core from candidate registry and then python3 on top of the s2i-base from candidate registry, and then we can test them together and create only one bodhi update.
Thanks for any help or advice.
you can use FQDN in FROM candidate-registry.fedoraproject.org/image. However that registry must be allowed in atomic-reactor config
Thank you but it does not solve my problem. I'd like to keep the official form of FROM in the dist git and use the parent id just for one rebuild to be able to push updates for all three images at once. Do you know who or where to ask about this? I think this might be a really useful feature for all maintainers.
if that's just for one rebuild, you can use --koji-parent-build and provide parent koji NVR in koji CLI
Are you sure? Could you please provide an example of NVR? I was trying to find it in the code of atomic-reactor and I've found that the provided parent-build is cast to an integer which makes me think that it should be a numeric build id.
ah sorry my bad, it's not build NVR but indeed build ID --koji-parent-build=1900853