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

How do you deploy only the files that have changed?

The Bamboo Salesforce CI workflow deploys everything listed in the package.xml regardless of whether it actually changed or not. This vastly increases the size and time of the deploy and seems like it can lead to accidental deployments. Is there any way to limit the deployment to only a specific commit (or list of commits)? Before the comments system was changed @Melanie Wright suggested that the scripts written by alexander brett at https// might provide a solution. Was Atlassian ever able to test those scripts or find some other solution?

4 answers

Hi @Melanie Wright, @Aditya Rawat, @Bryan Lucas,

Have provided an explanation of how we do partially deploy here:

Please note that while partial deployments are quicker, it makes it more likely to break things in your environment. This is because Salesforce deployment APIs don't check integrity on the entire metadata when deploying partially. For example you could change the signature of a method in a class and deploy it successfully, however if that method was referenced by another component which is not part of the deployment, you will now know about it at deployment time. Therefore this is practice that might be more suitable upstream (i.e. in your development sandboxes) and should be accompanied by running unit tests, if you have good coverage.

0 votes

Hi @Bryan Lucas,

We haven't tried out the Sophos scripts yet. Looking forward to spending some time on this in the future.. just not quite there yet. Would love to hear how it goes for you!

We haven't had trouble with accidental deployments much because we can see the diff between what is production vs downstream before we merge the code to trigger a deploy. The changes are nicely highlighted, but there can definitely be xml fatigue where we could miss something. 

@Bryan Lucas / @Melanie Wright I had been looking for the same solution where ideally the CI only deploys the metadata that was added in the recent commit however unable to find the @Alexander Brett's script at ?

I would like to try it out and give my feedbacks.


Hi @Aditya Rawat, checked in with the folks at Sophos and the best way to reach them is to create an issue on their GitHub project. Hope all goes well!

Hi @Aditya Rawat, Were you able to implement the solution to deploy just the committed files? can you pls share your approach on this.


Anybody implemented the solution to deploy just the committed files?  if yes can you please share the implementation.



Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo Data Center - Early Access Program

G’day Bamboo customers, The wait is almost over! We are in the final stages of work on the first release of Bamboo Data Center, our self-managed enterprise offering of Bamboo. This Data Center offe...

945 views 0 16
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