-
Bug
-
Resolution: Fixed
-
Minor
-
None
I've found with certain Hudson jobs, the polling logs always indicate that the workspace is dirty. I.e. I get a log like this:
Started on Jun 23, 2010 9:50:31 AM Looking for changes... Using remote perforce client: hudson-Foo-1234567890 [Foo] $ "C:\Program Files\Perforce\p4.exe" workspace -o hudson-Foo-1234567890 Saving modified client hudson-Foo-1234567890 [Foo] $ "C:\Program Files\Perforce\p4.exe" -s client -i Last sync'd change was 123456 [Foo] $ "C:\Program Files\Perforce\p4.exe" changes -m 2 //hudson-Foo-1234567890/... Latest submitted change selected by workspace is 123456 Assuming that the workspace definition has not changed. Done. Took 1.3 sec
The downside of this is a needless command to perforce editing the workspace every time the polling fires.
This doesn't happen for all of our jobs, but I can't find the significant difference. My inspection of the source didn't find anything immediately odd.
I don't expect this to be solved immediately, but would it be possible to add some logging somewhere to indicate why a workspace is marked as dirty at least?