[ci] CI should fail on bad builds#1238
Merged
Merged
Conversation
Signed-off-by: Chris Cranford <chris@hibernate.org>
|
🎊 PR Preview has been successfully built and deployed to https://debezium-debezium-github-io-preview-pr-1238.surge.sh
|
mfvitale
approved these changes
Mar 25, 2026
Signed-off-by: Chris Cranford <chris@hibernate.org>
Naros
force-pushed
the
test-ci-fails-bad-builds
branch
from
8cae8a7 to
62fe4ee
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR does the following:
rakecall out tosystemfails, we make sure that the error code is propagated back up to the GHA runtime. So, in the case of the YAML incident, this PR would fail, as is evident in this PR.If this looks good, I just need to remove the test commit to illustate the behavior.