-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
RHEL5
Hudson 1.382
Perforce Plugin 1.1.12
Perforce Polling Log
Started on Dec 12, 2010 3:21:16 PM
Looking for changes...
Using node: enhfamdev04
Using remote perforce client: hudson-18-540779238
[fnr-ces-1.1.2] $ /usr/local/bin/p4 workspace -o hudson-18-540779238
[fnr-ces-1.1.2] $ /usr/local/bin/p4 login -p
[fnr-ces-1.1.2] $ /usr/local/bin/p4 -P DE21CC451E206229E09883668325435D workspace -o -hudson-18-540779238
Changing P4 Client Root to: /foo/bar
Changing P4 Client View from:
Changing P4 Client View to:
//...<snip>.../ReleaseCandidates/V1.1.2/... //hudson-18-540779238/...
Done. Took 0.54 sec
Changes found
- duplicates
-
JENKINS-8064 Perforce plugin incorrectly finds changes
-
- Resolved
-
[JENKINS-8294] Polling Perforce always detects changes, even when there are none
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 138404 ] | New: JNJira + In-Review [ 187987 ] |
Component/s | New: p4-plugin [ 19224 ] | |
Component/s | Original: perforce-plugin [ 15506 ] |
There's a fix in 1.1.13 that helps alleviate this issue a bit, but the underlying problem has yet to be fixed in core.