Cherry-pick #17358 to 7.x: CI Hotfix #17363
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.
Cherry-pick of PR #17358 to 7.x branch. Original message:
What does this PR do?
The Jenkinsfile rules prevent many tests that should have been run to
execute. This changes tries to unify rules between the Jenkinsfile and
travis setup a little more.
Example PR that should have triggered almost all CI jobs, but they've all been skipped: #17332
Why is it important?
I noticed that in some PRs required tests have not been run at all by Jenkins. This is an attempt to applying similar rules to Jenkinsfiles and Travis setup.
Checklist
~~- [ ] My code follows the style guidelines of this project
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.~~
Related issues