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,459,905
Community Members
 
Community Events
176
Community Groups

Custom pipeline configuration with parallel steps

I am having trouble determining if it is currently possible in Bitbucket Pipelines to have multiple custom configurations that also execute a parameterized script with different arguments passed to it in parallel.

What I am trying to accomplish

  1. Have pipeline config for more than one "build-push" job to trigger on push to a branch
  2. Retain the ability to parallelize our scripts

This shows essentially what I'm currently attempting to do, but this fails with

"There is a YAML syntax error in your bitbucket-pipelines.yml at [line 45, column 11]. To be precise: found unconstructable recursive node"

Screen Shot 2022-04-22 at 10.09.27 AM.png

 

This Pipeline config is very close to what we want, but doesn't provide the custom "build-push" trigger.  Parallelization works as expected.

Screen Shot 2022-04-22 at 10.45.37 AM.png

Is this type of config currently possible in Pipelines?  

Thanks!

Ash

1 answer

0 votes
Caroline R Atlassian Team Apr 29, 2022

Hi, @ash, thank you for reaching out to Atlassian Community. 

As we'll need to see the YML file to further analyze this case, I have created an internal ticket for you using the email of your community account, so you don't have to share this information here. 

You should have received an email with a link to the support ticket. Just in case you haven't received it, please feel free to let me know and I can post the ticket URL here. The ticket will be visible only to you and Atlassian staff, no one else can view its contents even if they have the URL.

Please feel free to let me know if you have any questions.

Kind regards,
Caroline

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events