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

Do Bitbucket Pipeline have "rules" / "only-except" like in gitlab CICD Edited

HI all,


I trying deploy micro-services with multiples container in same bitbucket repository. currently.


For some newly added features, only some of the container will be modify, and I would like to avoid all container build again in "build" step (Noticed that there could be control over branches, but controlling step within the branch ? ).


In gitlab, Its allow some sort of control on job (step in bitbucket) so that it could avoid container without modification be re-build again and hence avoid wasting build time.

docker build: script: docker build -t my-image:$CI_COMMIT_REF_SLUG . rules: - changes: # Will include the job and set to when:manual if any of the follow paths match a modified file. - Dockerfile when: manual

Run manually if Dockerfile has changed OR $VAR == "string value"


Is there already such feature ? if not, would it be on product roadmap ?


- using GCP

- my situation (used docker-compose to develop locally, for a single service with multiple backend micro-services)


Looking forward to your advise !


1 answer

0 votes

Hi Solomon,

At the moment there is no built-in support for having these types of conditions on steps being triggered.

We an open feature request for triggering pipelines after certain files change. Which you can follow.

You can also open a new feature request here:!default.jspa



Hi Phil,

Thanks for the update, hope this feature request could be adopted and rollout soon!



Suggest an answer

Log in or Sign up to answer
Community showcase

All you wanted to know about customer support KPIs

When working in customer support, it’s crucial to calculate, analyze and monitor specific numbers, called KPIs (Key Performance Indicators). They go hand-in-hand with customer satisfaction, problem d...

122 views 1 5
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