I'm trying to configure an automated nightly build that will only produce a build if changes have been committed to the SVN repository since the previous nightly build. I am sure this was working at one point but now the SVN STATUS action seems to be failing to detect Newer Revisions.
Here's the log from an action where I've deliberately committed a new revision to a single file (Flow.dpr):
Executing external process: C:\Program Files\SlikSVN\bin\svn.exe
Starting Directory: c:\build\flow
Parameters: status --non-interactive --show-updates alpha -u
Output from C:\Program Files\SlikSVN\bin\svn.exe
* 939 alpha\Flow.dpr
Status against revision: 940
Total Items Modified : 0
Total Items Unmodified : 1
Total Items Added : 0
Total Items Delete : 0
Total Items in Conflict : 0
Total Items related to Externals Definition : 0
Total Items Ignored : 0
Total Items Not Under Version Control : 0
Total Items Missing : 0
Total Items with Type Mismatch : 0
Total Properties Modified : 0
Total Properties UnModified : 1
Total Properties in Conflict : 0
Total items Unlocked : 1
Total items Locked : 0
Total items with History with Commit : 0
Total items Switched : 0
Total items with Newer Revisions : 0
Action failed due to "Fail Action If" conditions
Subversion status failed with return code 0
Command line was : svn status --non-interactive --show-updates alpha -u
I've emboldened the lines that I think are of significance.
The log seems to indicate that the action is correctly identifying the file as not having been modified (in the "working copy"), which is showing as "Unmodified = 1". But although the status report itself clearly shows that the file has a newer revision in the repository (the '*' in the status report), the action is failing to acknowledge the Newer Revision.
I'm reporting this as a bug. Is this right, or have I missed something in my setup?