-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Platform: All, OS: All
Hi, since a while I have noticed a very strange behavior in Hudson. After a
commit to subversion it starts building the project, and after completion it
starts to build it again and again ad infinitum. This happens in 1.156 and also
in 1.177
The subversion polling always reports that changes are found, but there are no
changes:
Started on 01.02.2008 09:52:40
Revision:27534
Revision:28031
(changed from 27992)
Done. Took 0 seconds
Changes found
The build then starts with this message (servername replaced with xxxxx):
started
Updating https://xxxxxxxx.xxx/koagent/trunk
Fetching external item into 'D:\hudson\jobs\KoAgent
Style\workspace\trunk\lib\required\ensure4j'
External at revision -1
At revision 28031
Fetching external item into 'D:\hudson\jobs\KoAgent
Style\workspace\trunk\src\ensure4j'
External at revision -1
At revision 28031
At revision 28011
no change for https://xxxxxxxx.xxx/koagent/trunk since the previous build
no change for https://xxxxxxxx.xxx/lib/ensure4j/trunk/lib/required since the
previous build
no change for https://xxxxxxxx.xxx/lib/ensure4j/trunk/src/java since the
previous build
[trunk] $ cmd.exe /C '"ant.bat clean test.style && exit %%ERRORLEVEL%%"'
Buildfile: build.xml
...
The workspace shows that hudson is checking out an old version of
https://xxxxxxxx.xxx/koagent/trunk, it does not use the latest version! This
happens with both "Use update" and without the option (There the workspace is
correctly deleted, and the freshly checked out version is still not the last
version in subversion).
- is duplicated by
-
JENKINS-1043 SVN polling reports change, but an older revision is checked out
- Closed