My appologies if this has been asked already. Is it possible to setup a deployment task such that, it's not the entire artifact that is being SCP'd to a remote server, but rather just the files between effected since the previous deploy?
Beanstalk has a nice deploy feature such that they drop a .revision file into the location where you deploy. That file contains the sha of the last revision which was deployed. When a new deploy occures, the .revision is checked against what is going to be deployed, and only the files which are different between the two revisions are sent. Any deleted files are also removed from the target server.
Does bamboo have similar ability? Or is it necessary for all files to be deployed each time, regardless of whether they are actually different from what's already been deployed?
I'm John Allspaw, co-founder of Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs