..." or perhaps just track the svn revision numbers when you deploy so you can find the differences for subsequent updates."
This is actually where I was headed but I am unsure how to do this exactly. In theory I can compare differences between revision 100 and revision 102, and loop through the new files and apply them, but in practice I am not exactly sure how to implement. On Fri, Apr 26, 2013 at 1:18 PM, Les Mikesell <[email protected]> wrote: > On Fri, Apr 26, 2013 at 11:53 AM, Maureen Barger <[email protected]> wrote: >> They are in SVN. I am trying to figure out the best way to leverage >> svn and jenkins to get the files. Liquibase really didn't fit our >> needs at the time we worked with it. > > Jenkins should show you a list of changes between builds, but I > wouldn't rely on always deploying every build to every target if you > are thinking in terms of jenkins-managed deltas. You might let > jenkins archive full copies of each file you need with each build, or > perhaps just track the svn revision numbers when you deploy so you can > find the differences for subsequent updates. > > -- > Les Mikesell > [email protected] > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
