I have been trying to create a bamboo.yaml that both creates new plan branches for pull requests and plan branches for all release/.* branches.
Is it possible to create a specification that has different integration for different plan branches?
branches:
create:
for-new-branch: release/.*
delete:
after-deleted-days: 14
after-inactive-days: 14
branches:
create: for-pull-request
integration:
merge-from: ${bamboo.repository.pr.targetBranch}
push-on-success: false
link-to-jira: true
I don't want the release branches to merge with anything when built but plan branches from PRs should always be merged with the target branch.
Hi Andreas
I'm looking for the same thing. Did you find any solution?
I never did. We reverted back and are not using specs anymore.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oh ok. After digging deeper today I found Bamboo 7.1 supports branch overriding for several things including branch-config -> integration.
I have to update to Bamboo 7.1 so I haven't tested yet.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did anyone get this to work? I want exactly the same thing.
Normal development branches are created by pull-request, and those have a merge strategy. But a release branch should be created just from a named branch, and it should not merge.
I have created the YAML spec from how I understand it should be, but it doesn't do anything.
branches:
create: for-pull-request
delete:
after-deleted-days: 0
after-inactive-days: 60
integration:
push-on-success: false
merge-from: core-build
link-to-jira: true
branch-overrides:
-
^test_.*$:
branch-config:
create:
for-new-branch: ^test_.*$
delete:
after-deleted-days: 0
after-inactive-days: 5
link-to-jira: true
I create a branch in git matching the regex, but I still don't get any branch appearing automatically.
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.