Hello Glenn, On Fri, Jun 17, 2016 at 6:42 PM, Metster <e...@patchworks.net> wrote:
> We are using Jenkins and would like to only build and deploy the latest > changes since the previous build but I'm not sure how to do this. Right > now it is deploying the entire SVN on every build and since it is 1.6Gb, it > takes 6 hours. > What commands does Jenkins run? I guess that this Jenkins job is currently configured to run `svn export` <https://www.visualsvn.com/support/svnbook/ref/svn/c/export/> command. Checkout and update a working copy instead of exporting the repository contents, Subversion won't have to download all the 1.6 GB in such case, it will fetch only changed items. You could `svn checkout` <https://www.visualsvn.com/support/svnbook/ref/svn/c/checkout/> a working copy and run `svn update` <https://www.visualsvn.com/support/svnbook/ref/svn/c/update/> it to update it to the latest or some particular revision. This is the correct and I guess most common approach that should be used by CI or build machines. The process is described in SVNBook | Creating a Working Copy <https://www.visualsvn.com/support/svnbook/tour/initial/> & Update Your Working Copy <https://www.visualsvn.com/support/svnbook/tour/cycle/#svn.tour.cycle.update> sections. <https://www.visualsvn.com/support/svnbook/tour/initial/> -- With best regards, Pavel Lyalyakin VisualSVN Team -- You received this message because you are subscribed to the Google Groups "VisualSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to visualsvn+unsubscr...@googlegroups.com. To post to this group, send email to visualsvn@googlegroups.com. Visit this group at https://groups.google.com/group/visualsvn. For more options, visit https://groups.google.com/d/optout.
