Hi Shanz, We do also archive executable (jars) in jenkins for various reasons.
To avoid the out of synch issue that you mention, we create a tagged (i.e named) backup of the sources via a "svn copy" in the subdir /tags of our svn. Then, we check out the source from there, compile it and commit executable back: this way the issue that you mention doesn't show up. PS: svn copy has 2 nice features: it is optimized (the files are not really copied, just backlinked to their souce) and the modification history is preserved for the copies. regards didier Le jeudi 29 mars 2012 16:10:35 UTC+2, shanz a écrit : > > This is a subversion question rather than a Jenkins one I suppose. > Our build on Jenkins takes several hours. Assume the build begins > with svn revision 700. > If someone commits to Jenkins' trunk (making revision 701) during > those build hours, then the resultant executable is out-of-step with > the repository. We want to commit the resultant exe. So the exe will > be on revision 702 but the exe wasn't built with the features > introduced with revision 701. > > Is this a common problem? Any solutions?
