This repository has been archived by the owner on Oct 28, 2024. It is now read-only.
[jjbb] optimise with push events #648
Merged
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
cachedout
approved these changes
Jul 3, 2020
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
|
kuisathaverat
approved these changes
Jul 3, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What does this PR do?
It changes the behaviour to build PRs when Jenkins makes a scan, instead of trigger all PRs if the target branch has changed, the builds are only triggered if there's changes in the PR and we did not test them.
Why is it important?
With the amount of PRs and branches that this repo has built all PRs on changes in the master is not an option, we would use all the resources we have and we block the real builds we need to make.
Issues
Similar to elastic/beats#19510