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?
What we do is tag the deployable artifacts each time then figure out what's changed. Then we only deploy those files.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.