Details
-
Suggestion
-
Resolution: Fixed
-
None
Description
It looks like when defining a deployment trigger in cron format, overriding the branch is not supported. Can we add the functionality so when defining a branch in the yml specs, this maps to the current `Use a custom plan branch` option on the trigger configuration.
suggested syntax:
triggers: - cron: expression: 0 0 * * ? * branch: <branch>
Attachments
Issue Links
- is duplicated by
-
BAM-21729 Scheduled deployment trigger doesn't support custom branch at YAML Specs
- Closed