Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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
Community showcase
Published in Bitbucket Pipelines

Bitbucket Pipelines Runners is now in open beta

We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...

684 views 15 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you