Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,557,742
Community Members
 
Community Events
184
Community Groups

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

Vinh Hong
Vinh Hong Sep 11, 2019

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

 

Answer
Watch
Like Be the first to like this
747 views

2 answers

0 votes
Vinh Hong
Vinh Hong Sep 16, 2019

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?

View More Comments
Alexey Chystoprudov
Alexey Chystoprudov
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 17, 2019

See screenshot

Capture 2019-09-17 at 11.34.16.png

Like
Vinh Hong
Vinh Hong Sep 17, 2019

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.

Like
Reply
0 votes
Alexey Chystoprudov
Alexey Chystoprudov
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 14, 2019

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

Reply

Suggest an answer

Log in or Sign up to answer
Bamboo
Bamboo
TAGS
AUG Leaders

Atlassian Community Events

See all events