Jenkinsfile: Disable Quality gate for maven warnings #969 #1007
Conversation
This file contains 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
…#969 should be revert if eclipse-platform#969 is fixed
|
only warnings, no errors => success |
The warnings are about an possible instability in build, therefore they vary dependent on the build execution order (and that's what the warning is complaining about) so it can never be constant. |
This was referenced Dec 18, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
should be revert if #969 is fixed
The Problem is, that almost every build fails because the number of warnings is too flaky and independent of the PRs that they should verify. If they would be at least constant they would not fail the PRs.