-
Notifications
You must be signed in to change notification settings - Fork 23
🌱 Allow downloading artifacts to allow pre-preparing directories for image-building #1117
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
Conversation
lentzi90
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks ok to me
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lentzi90 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…age-building Signed-off-by: peppi-lotta <[email protected]>
c8405a8 to
c59596b
Compare
tuminoid
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
|
/override metal3-ubuntu-e2e-integration-test-main |
|
@tuminoid: Overrode contexts on behalf of tuminoid: metal3-ubuntu-e2e-integration-test-main In 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. |
What this PR does / why we need it: A docker image building requires that all the element needed for building are in the same directory or sub directory where the
Dockerfileis located. This is why I created a PR that prepares FKAS for image building by moving the required CAPM3 directory into the Fake-apiserver directory before building.Because we are using a reusable workflow for image building, the directory prep has to be done in a separate job. It seems changes are not retained across jobs even when they are run in the same workflow. I'm suggesting to use the upload-archive and download-archive actions to pass the pre prepared FKAS folder from one job to another.
Related PR in CAPM3 can be found here: metal3-io/cluster-api-provider-metal3#2846