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?
