Fail fast for poetry install
command
#1349
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In case the
poetry install
command fails, we probably don't want to continue in the execution anymore, so let's have a fail fast check there.This is a candidate for backport to
releases/2.8.0
branch.Why I want it now? Looks like our pre-created environment against
master
branch may be a bit fragile when running agasint some older branch - this means that packages should be downgraded/update/removed, etc. Don't know the reason and also I'm not sure whether this fail-fast will work since I wasn't able to reproduce the issue, but it shouldn't harm, right? 🙃FYI here is an example of the job run failed poetry environment from our Jenkins: