Hi there, I've never used tagOnSuccess, but does it automatically commit before tagging?
If not, 1) CC.NET checks out/updates your working copy to rev 1 2) You modify the RC file 3) CC.NET runs the build scripts 4) On success, CC.NET tags rev 1 5) Your modified RC file is not in rev 1 Can you add a conditional commit? 4) On success a) Commit working copy to rev 2 b) CC.NET tags rev 2 On Thu, Oct 15, 2009 at 2:49 AM, Hwee Miin Koh <[email protected]> wrote: > > I'm using CCNET v1.4.3 and SVN v1.5.5 to setup continuous integration > environment for c++ projects. > > I'm using a plugin to make use of svn revision to generate label in > the form of "major.minor.revision.build", with another plugin to > update the .rc file in the CCNET working directory during build, and > have CCNET create tag on svn (by setting tagOnSuccess to true) after a > build completed. However, I discover that when the build is trigger by > modification on svn, the changes made to the .rc during build is not > reflected on the created tag, the changes made to the .rc during build > only reflected on the tag if the build is triggered by force. > > Is there anyway to force CCNET to always create tag using CCNET > server's local working copy? >
