I have my build plan setup to auto create branches that match a regex (such as 'release-xx' or 'hotfix-xx') however I don't see how I can automatically deploy those branches which Bamboo is adding via regex? The Deploy triggers on successful builds seems to require an exact branch name...
I have the same problem/question. I would like to add a trigger for an automatically created plan branch.
Our team is working as described in the GIT workflow: https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow
We need it for the release branches. There is only one active release branch at a time. The plan branch is created automatically, and any pushes to it should trigger a deployment. For now, we are adding a trigger for each release manually. But it would be handy to have this automated.
It would be nice to be able to use a wildcard/regex in the trigger configuration, as it is possible for the creation of plan branches. Something like "release/\d+.\d+" or "release/*"
Kind Regards
Well, Bamboo doesn't allow automated creation/deploying of Deployments for new branches. I'm not really sure how your workflow works - can you provide more details on that?
I think that creating/deploying automatically would be a mess: these deployments would overwrite deployments from other branches in an uncontrollable way.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have this need for NuGet packages.
We want to be able to trigger deployments for alpha (development), beta (release/*), and production (master) channels.
We're stuck on the beta releases for this very issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.