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,456,925
Community Members
 
Community Events
176
Community Groups

How can I define a rule to matching target branch name at pull-request section in yaml file?

I have been read over https://support.atlassian.com/bitbucket-cloud/docs/configure-bitbucket-pipelinesyml#pull-request and https://support.atlassian.com/bitbucket-cloud/docs/use-glob-patterns-on-the-pipelines-yaml-file/
All of this is talk about how to define glob patterns to matching "from branch" name , but I need to define a rule to match "target branch" name at pull-request section in yaml file.

Overall , I want scripts can work like this:

  • when a pull request is from branch task/fix-404-bug to target branch relase/app-1.0.0: 
    • match the pattern , do some scripts.
  • when a pull request if from branch task/add-a-button to target branch feature/new-main-page
    • match pattern fail, don't do this scripts.

Can I do like this in yaml file ? Or it only just support to match from branch name?

 

1 answer

1 accepted

0 votes
Answer accepted

Hi @QiangShen,

I'm afraid that this is not possible at the moment, pull-requests definitions match the source branch only.

We have a feature request for what you are asking in our issue tracker:

Since you'd be interested in that, I would suggest adding your vote to that ticket (by selecting the Vote for this issue link) as the number of votes helps the development team and product managers better understand the demand for new features. You are more than welcome to leave any feedback, and you can also add yourself as a watcher (by selecting the Start watching this issue link) if you'd like to get notified via email on updates.

Implementation of new features is done as per our policy here and any updates will be posted in the feature request.

In the meantime, you can check the workaround used by one of our other customers:

https://jira.atlassian.com/browse/BCLOUD-17859?focusedCommentId=2651735&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-2651735

You still need to determine the source branch in pull-requests, but during the build you can check the destination branch and fail the build if it doesn't match the desired branch(es).

Kind regards,
Theodora

Fully appreciate for you answer.

It just met all I want to know. 

I will use the workaround for now.

Thanks Theodora!

Like Theodora Boudale likes this

You are very welcome, please feel free to reach out if you ever need anything else!

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events