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,457,208
Community Members
 
Community Events
176
Community Groups

Is it possible to fail the step from where a remote pipeline is called through trigger-pipeline ?

Hello,

 

I am using atlassian/trigger-pipeline:5.0.0 without any issue. It triggers the pipeline and it waits for the remote pipeline to finish. All that works perfectly.

However, It is mandatory for my use case that the pipeline/step from where I am calling the other pipeline, follows the status of the remote pipeline.

Currently, if the remote pipeline fails, atlassian/trigger-pipeline ony shows a red message, but the step is marked as success. What I need, is that if the pipeline that is being called fails for any reason, the step from which I am calling it, also fails.

Is there any strategy or workaround to accomplish this?

Thanks

Juan

 

1 answer

0 votes

Hi Juan,

I assume that you are using the variable WAIT: 'true' in the definition of the pipe?

If set to true, the pipe will wait for the triggered pipeline to complete. If the triggered pipeline fails, the pipe should also fail and the step with the pipe should fail as well.

I am unable to reproduce the behavior you are describing using the same version of atlassian/trigger-pipeline pipe.

I would suggest creating a support ticket for this issue so we can further investigate. The support ticket will be visible only to you and Atlassian staff, so you can share the URL of a build that uses this pipe and we can look into this.

I see that you are an admin of a workspace on a paid billing plan that uses Pipelines. If the issue concerns a repo of that workspace, you can create a ticket via https://support.atlassian.com/contact/#/, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product.

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

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events