-
Bug
-
Resolution: Fixed
-
Low
-
8.0.0
-
None
-
Severity 3 - Minor
-
Issue Summary
Bitbucket Server trigger can't be used at YAML Specs for plan triggers configuration.
Steps to Reproduce
- Create plan with Bitbucket Server trigger
- Export config to YAML Specs
Expected Results
Full plan config can be exported to YAML format
Actual Results
For Bitbucket Server trigger you see
# Trigger type TriggerProperties{name='Bitbucket Server repository triggered', description='', conditions=[com.atlassian.bamboo.specs.api.model.trigger.AllOtherTriggerConditionProperties@c9576315], enabled=true} is not supported yet #
Workaround
Bamboo versions >= 8.0.6, 8.1.2, and 8.2.0
The Bitbucket trigger won't show up if it's the only trigger on the plan. As a workaround you can:
- Temporarily add another trigger to your plan (e.g. Repository polling).
- Export the config to YAML Specs again.
- The config will include both triggers now – remove the polling trigger from the config if it's not needed before importing the YAML file.
Bamboo versions < 8.0.6, 8.1.2, and 8.2.0
- Use Java Specs format instead of YAML.