-
Suggestion
-
Resolution: Fixed
-
None
Problem Definition
YAML can be configured with multiple repositories through checkout task. However, trigger in YAML could not be configured to enable trigger for certain repository only.
If a single repository is used to manage YAML Specs for multiple plans, a Specs change in a plan will trigger normal builds for all the related plans (if there are 50 plans affected, 50 builds will be added to the queue). This will flood the queue and will take some time for the agents to clear the queue.
Suggested Solution
Configurable trigger setting in YAML so that only certain repository change will trigger the plan
Workaround
Configure exclude function at Administration >> Linked repositories >> <repoName> >> Change detection options to exclude file pattern "bamboo-specs/.*"
[BAM-20932] Trigger repository configuration in YAML
Remote Link | Original: This issue links to "Page (Confluence)" [ 562647 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
Comment |
[ +1 from me
Tiny change for functionality that bamboo already supports. Would be really useful for our projects. ] |
Status | Original: In Progress [ 3 ] | New: Waiting for Release [ 12075 ] |
Remote Link |
New:
This issue links to "+core+ Dogfooding › Test Git Branch Detection › |
Fix Version/s | New: 8.1.0 [ 97096 ] |
Status | Original: Gathering Interest [ 11772 ] | New: In Progress [ 3 ] |
Assignee | New: Alexey Chystoprudov [ achystoprudov ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 562647 ] |