Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,359,752
Community Members
 
Community Events
168
Community Groups

How do I configure YAML specs to trigger the deployment from a specific branch?

According to the doc, I can configured my spec as follow.  But scanning is failing stating that it is unable to locate the triggering branch "dev-branch".  I have dev-branch in my current linked repo.  What is missing?

#----------------------- Dev Environment -----------------------------                
Dev:
  triggers:
    - build-success:
        branch: dev-branch

 

2 answers

I'm not quiet understand the instruction above.  Can you provide screen shot as to where I can find the plan's branch name?

My understanding is that plan is already associated to the repository branch, during repository linking.  Am I suppose to create a branch manually in Bamboo plan?

See screenshot

Capture 2019-09-17 at 11.34.16.png

What?  I have to do a half configurations in YAML Specs, follow by manual update in Bamboo configurations, and then go back to YAML Specs to add the configurations?  Wow what a clumzy way for a configuration as code (CaC).

Also, since I purchase a license of Bamboo, isn't any support to fix the above issue?  At lease some kind of fix to allow scanning not to failed.  This is BAD product.

0 votes

Branch name should be the same as name of Plan branch in Bamboo. Not branch name in repository.

Branch name can be found at Display name field at screen by link http://localhost:8085/branch/admin/config/editChainBranchDetails.action?planKey=BRANCH-KEY

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 9.0 is now available

Hey there, Data Center community! I'm Martyna Wojtas and I am the Product Manager for Bamboo Data Center. I’m excited to share that Bamboo 9.0 is now available. We purpose-built this platform to help...

301 views 0 7
Read article

Atlassian Community Events