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,552,838
Community Members
 
Community Events
184
Community Groups

Process matching pipelines stages sequentially

Edited

For a bitbucket-pipelines like this:

pipelines:
  default:
    - step:
        script:
          - doA
  branches:
    '*':
      - step:
          script:
            - doB # we are here if default ran its steps (doA) successfully
    staging:
      - step:
          script:
            - doC # we are here if default and branches '*' ran their steps (doA then doB) successfully
    production:
      - step:
          script:
            - doC # we are here if default and branches '*' ran their steps (doA then doB) successfully

 

I'd expect that default is ran every time, whatever follow (currently it's not the case, default is only ran if there's nothing else matching)

I'd also expect that each matching branches pattern are ran, in order (currently only last one is ran) 

You could add a mode: sequential in the pipelines root properties, or at least a `shared`  property under pipelines, ran in all cases

"Pipeline" in Computing means a set of tasks connected in series, that's why the current behavior is confusing

It'd be possible to put everything under `default` and use `BITBUCKET_BRANCH` case conditions, but that's not very readable and not easy in yaml

Thanks

 

note: the html editor is not working well with code and pasting, Ii had to format this post from the dev console `$0.textContent = `pipelines:...`

0 comments

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events