-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Wrap nop final step with entrypoint #748
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester 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 |
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.
sounds informative!
12a477e
to
5c04904
Compare
You already mention the other PR to remove the |
@nader-ziada Right, the only thing is that #715 is on hold, quoting @dicarlo2
While waiting we may want to fix the wording 👼 That said I'm also ok closing this one and waiting for a resolution on #715 😉 |
/hold |
`nop` image/step used to be executed *only* when all the previous step were done sucessfully. As we are not using init containers anymore, this is not true, `nop` will always be executed even in case of previous failure (after the others though). This happens because we don't use the `entrypoint` wrapper for this final step. This fixes it by wrapping `nop` with entrypoint — just like other steps. That way, it will only print `build successful` in case of actual successful run 💃 Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
5c04904
to
1ea0766
Compare
/hold cancel |
nice fix @vdemeester 👏 |
/lgtm |
Changes
nop
image/step used to be executed only when all the previous stepwere done sucessfully. As we are not using init containers anymore,
this is not true,
nop
will always be executed even in case ofprevious failure (after the others though). This happens because we
don't use the
entrypoint
wrapper for this final step.This fixes it by wrapping
nop
with entrypoint — just like othersteps. That way, it will only print
build successful
in case ofactual successful run dancer
Related is #715, but in the meantime,
we may want to print something less misleadingwe may want to fix that 👼cc @nader-ziada
Signed-off-by: Vincent Demeester vdemeest@redhat.com
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide
for more details.