CI: limit push trigger to primary branches #6710
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
mbien
added
CI
|
I interpret the thumbs up as go ahead with merge :) |
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.
Limits automated CI to
master,deliveryandrelease*branchescontext:
CI is running currently 10h+ in tests on push to any branch of the netbeans repo. This was intended for trunk branches like
masterordelivery, but falls apart as soon someone uses a feature branch since it would test everything multiple times additional to the PR triggered tests.The second problem is cache size, since every root branch has a ~800mb footprint. During times with many concurrent dependency update PRs which write to the cache we can run out of cache.