-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
🌱 Avoid cd'ing into test folders when building Docker images #9744
Conversation
59de486
to
be394a7
Compare
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
LGTM label has been added. Git tree hash: d86817dc5c730869ae8827cd75116ef96650aaac
|
Signed-off-by: Stefan Büringer [email protected]
be394a7
to
e1ae606
Compare
Pushed a fix |
/lgtm |
LGTM label has been added. Git tree hash: 51eb25946b72d669b546cf5a1171151a1408bf01
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini 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 |
/lgtm++ |
Signed-off-by: Stefan Büringer [email protected]
What this PR does / why we need it:
Looks like we currently get (at least) the test/extension binary in some of our CAPD images for some architectures. Potentially more provider / architectures are affected.
We are currently guessing that running
make release-staging
with-j 8 -O
triggers this behavior. Basically we guess that the cd commands are getting mixed up with the docker build commands and then we produce CAPD images based on the wrong Dockerfile which then builds the test/extension.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #