-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Hudson 1.379, Perforce plugin 1.1.9
I've seen a number of problems communicating with Perforce since upgrading to 1.1.9.
The build log mentions "No output for: " and then a perforce command (e.g. counter/workspace). The build then fails.
Usually the next build succeeds.
See attached file.
I've only seen it on slaves, i.e. remote clients.
- depends on
-
JENKINS-7809 Remote Launcher randomly returns no data.
-
- Resolved
-
- is duplicated by
-
JENKINS-7700 Perforce plugin failing occasionally with PerforceException: No output for:
-
- Resolved
-
-
JENKINS-8254 Intermittent errors where Perforce plugin can't communicate with Perforce
-
- Resolved
-
- is related to
-
JENKINS-8064 Perforce plugin incorrectly finds changes
-
- Resolved
-
[JENKINS-7664] Exceptions when communicating with Perforce "No output for:" (probably slave-only)
Assignee | New: Rob Petti [ rpetti ] |
Link |
New:
This issue is duplicated by |
Link |
New:
This issue depends on |
Link |
New:
This issue is related to |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Resolution | Original: Fixed [ 1 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Attachment | New: perforce.hpi [ 20021 ] | |
Attachment | New: JENKINS-7664.diff [ 20022 ] |
Link |
New:
This issue is duplicated by |
Attachment | New: perforce-rpetti-54.hpi [ 20179 ] |
Link |
New:
This issue is blocking |