Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

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,463,881
Community Members
 
Community Events
176
Community Groups

How to add branches starting with release under 'Branches allowed to deploy' in Repository settings?

I have more than 2 Release branches and will be more in future I want to add all the branches starting with Release to the 'Branches allowed to deploy' in repository settings-> Test environment, I am looking for any glob pattern, something like this : release/* , but not this as it is not working.

1 answer

0 votes

Hi @Gangadhar Malana and welcome to the community.

The glob pattern release/* should work if you are running builds based on branches and if the deployment step has the deployment keyword with the name of the environment where you set up this rule, e.g. like this:

- step:
name: Deploy to staging
deployment: Staging
script:
- echo "Deploy to staging"

 

  • Could you please let us know how you have configured builds in your yml file for release/* branches?
    Are they running as part of the default pipeline?
    Or do you have a definition for
    branches:
      release/*:
    Or a different setup?

 

  • Does the deployment step have the keyword deployment along with the name of the environment where you set up this rule?
  • When you say that this is not working, do you mean that commits in other branches trigger the deployment step as well?

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events