chore(ci): don't fail fast for build job #363
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.
Pull request checklist
Please check if your PR fulfills the following requirements:
npm run build
) was run locally and any changes were pushednpm test
) were run locally and passednpm run prettier
) was run locally and passedPull request type
Please check the type of change your PR introduces:
What is the current behavior?
If one CI job fails, others may be cancelled without running to completion
GitHub Issue Number: N/A
What is the new behavior?
this commit prevents the build job from failing fast (i.e. if '2' in the
stencil_version matrix fails, the rest of the jobs will not fail). this
ought to allow us to root our stencil version-based errors more easily
if an error pertains to a single version
Does this introduce a breaking change?
Testing
ddeeb46 was temporarily added to this branch to add a little bit of chaos/random error throwing. No jobs were cancelled as a result of errors being thrown
Other information