[Azure Pipelines] limit triggers to branches actually used #20441
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
Branches like epochs/six_hourly wouldn't do anything, but they create a lot of entries in the Azure DevOps dashboard: https://dev.azure.com/web-platform-tests/wpt/_build?definitionId=1 The no-op builds are mostly harmless, but make it harder to find the interesting builds.
LukeZielinski
approved these changes
Nov 26, 2019
| @@ -16,8 +16,12 @@ | |||
| # https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/v2-windows | |||
|
|
|||
| trigger: | |||
| - epochs/* | |||
| - triggers/* | |||
| - epochs/daily | |||
There was a problem hiding this comment.
Curious why only these epochs - worth a comment maybe?
There was a problem hiding this comment.
They're the only ones referenced in the following config, I'll add a comment.
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.
Branches like epochs/six_hourly wouldn't do anything, but they create
a lot of entries in the Azure DevOps dashboard:
https://dev.azure.com/web-platform-tests/wpt/_build?definitionId=1
The no-op builds are mostly harmless, but make it harder to find the
interesting builds.