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,463,370
Community Members
 
Community Events
176
Community Groups

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//github.com/sophos 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:

https://github.com/sophos/App-SFDC/issues/1

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.

Hi,

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

Thanks,

Harvin

@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 https://github.com/sophos ?

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.

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. 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events