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

Your Points Tracker
  • 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
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?
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

Start pipelines parallel steps if a condition is met Edited


We are running a project that has a core app, a landing page and a back-end all in the same repository.

The project has 3 different parallel steps that runs for each of the parts ie. main app, landing page or back-end.

At the moment all 3 are triggered and there is a check that stops the repository if there are no changes in the respective folder.

There are 2 problems with this setup:

  1. Each parallel step waste about 30 seconds of build time for no reason
  2. The return status should be "Pipeline Succeeded" but the checks make the whole pipeline to fail

Ideally I'd want run the folder update checks once in the main step and start the parallel steps only if there are changes.



1 answer

0 votes

Hello @LiveDuo

That is an interesting scenario indeed.

I've run a search in our issue system and happened to find an improvement request already filed for this: #16560 - Trigger pipeline only if certain files are changed. I guess that would cover your case.

I guess you need this problem solved now and therefore I have an idea to share that might help you to reduce the issue you are facing, but it will require an extra configuration. You would need:

  1. Create a custom pipeline for each deploy part.
  2. Both master and develop branch steps would have to check what deploy should run (evaluating the source code changes)  and based on that decision call the custom step accordingly.

These are the references you can use to move forward with this idea:

Please keep in mind that you would still have at least 2 steps running so you would save ~30s in the best scenario and lose 30s if you have changes in all software parts. It worth only depending on how often you have changes in all of them.

Does it make sense to you?
Please share your comments/thoughts.

Suggest an answer

Log in or Sign up to answer
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...

634 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