-
Bug
-
Resolution: Fixed
-
Major
-
None
-
P4-Plugin 1.4.4
Jenkins 2.8
Perforce Server version: P4D/LINUX26X86_64/2016.1/1429894 (2016/08/24)
The p4-plugin repeatedly builds a job that has been configured to delete the workspace in a post-build action.
I think this is perforce server dependent since it started happening yesterday after we upgraded to perforce server 2016.1 (previously 2013.1).
Polling log during running build
Perforce Software Polling Log
Started on Sep 1, 2016 9:45:00 AM
Polling SCM changes on virtnode4
P4: Polling on: virtnode4 with:jenkins-virtnode4-server_4.4.x_tests
... p4 client -o jenkins-virtnode4-server_4.4.x_tests +
... p4 info +
P4 Task: establishing connection.
... server: perforce:1666
... node: virtnode4
P4: Polling with range: 2048991,now
... p4 changes -m100 //jenkins-virtnode4-server_4.4.x_tests/...@___ +
Done. Took 41 sec
No changes
Polling after previous build has completed
Perforce Software Polling Log Started on Sep 1, 2016 9:47:57 AM No workspace is available, so can’t check for updates. Scheduling a new build to get a workspace. (nonexisting_workspace) Done. Took 35 ms Changes found