That is a bit odd. Success/failure of the SourceSafe action is determined by the exitcode of ss.exe. As a workaround, you could have two copies of the step, one marked to ignore failure and the second not.
Using multiple checkouts or actually failing the build if somebody has one of the assemblyinfo files checked out would be a more robust way to deal with it.
|