-
Notifications
You must be signed in to change notification settings - Fork 15
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
Support no-clone build-push mode #332
Conversation
e53adac
to
4b9327b
Compare
@edsantiago FYI I bumped out a bunch of timebomb dates in this PR b/c I only need to make the fedora-based build_push VM (so it can be tested). Is this going to mess you up in #331 ? |
Can you please merge 331? It's done. |
Cirrus CI build successful. Found built image names and IDs:
|
Yep, np, done. BTW, unless you need aa second-look, please feel free to just merge those PRs yourself. No reason for unnecessary administratia here 😀 |
4b9327b
to
c0cda20
Compare
As originally conceived, the build context for each image lives in the respective podman, buildah, and skopeo repositories. A future set of PRs will move both the source and build automation into the new containers/image_build repository. This is needed to support images that are point-in-time rebuildable and run test-builds on image context changes. Add a magic 2nd argument prefix ('.'), and conditionals to prevent cloning the build context repo. This will allow for an interim period where build automation can run from both the current and new repository until the context repos can be moved. Signed-off-by: Chris Evich <cevich@redhat.com>
c0cda20
to
565d822
Compare
Cirrus CI build successful. Found built image names and IDs:
|
I was partway through review. No showstopper concerns.
The no-surprises factor: making sure everyone knows what's going on in this repo. Thanks for merging it. |
Signed-off-by: Chris Evich <cevich@redhat.com>
Signed-off-by: Chris Evich <cevich@redhat.com>
Well I appreciate that. Just don't want you to feel obligated, should the need arise in some more urgent situation. |
As originally conceived, the build context for each image lives in the respective podman, buildah, and skopeo repositories. A future set of PRs will move both the source and build automation into the new containers/image_build repository. This is needed to support images that are point-in-time rebuildable and run test-builds on image context changes.
Add a magic 2nd argument prefix ('.'), and conditionals to prevent cloning the build context repo. This will allow for an interim period where build automation can run from both the current and new repository until the context repos can be moved.