When using 'p4.run("sync","//PATH/...") the Windows 10 slave drops the connection after 5 minutes every time. This was proven on a Webex using Wireshark.
If 'p4sync()' is used the command ran to completion (20 minutes). Potentially there is a problem with P4Groovy commands not displaying any output till the end of the command that is triggering this problem.
This ticket has been created to record the occurrence, allow me to try and reproduce the problem and to be a place holder where other reports of the same problem can be recorded.
Note: Cloudbees support were unable to find a problem on their side.
Example jenkinsfile (in editor):
pipeline{
agent{
label 'Win10'
}
stages{
stage('P4 Sync'){
steps{
script{
def p4 = p4 credential: 'MasterCredential', workspace: manualSpec(charset: 'utf8', name: 'CLIENT', pinHost: false, spec: clientSpec(allwrite: true, backup: false, clobber: false, compress: false, line: 'WIN', locked: false, modtime: false, rmdir: false, streamName: '', type: 'WRITABLE', view: '//depot/... //CLIENT/...'))
p4.run("sync","-f", "//depot/PATH/...#0")
p4.run("sync","-f", "//depot/PATH/...")
}
}
}
}
}
- is duplicated by
-
JENKINS-55209 p4 groovy commands with 300 second timeout
-
- Closed
-
- relates to
-
-
- Open
-
[JENKINS-58161] Agent time out with P4Groovy sync after 5 minutes?
Karl Wirth
created issue -
Karl Wirth
made changes -
| Assignee | New: Karl Wirth [ p4karl ] |
Karl Wirth
made changes -
| Description |
Original:
When using 'p4.run("sync","//PATH/...") the Windows 10 slave drops the connection after 5 minutes every time. This was proven on a Webex using Wireshark. If 'p4sync()' is used the command ran to completion (20 minutes). Potentially there is a problem with P4Groovy commands not displaying any output till the end of the command that is triggering this problem. This ticket has been created to record the occurrence, allow me to try and reproduce the problem and to be a place holder where other reports of the same problem can be recorded. +Note:+ Cloudbees support were unable to find a problem on their side. |
New:
When using 'p4.run("sync","//PATH/...") the Windows 10 slave drops the connection after 5 minutes every time. This was proven on a Webex using Wireshark. If 'p4sync()' is used the command ran to completion (20 minutes). Potentially there is a problem with P4Groovy commands not displaying any output till the end of the command that is triggering this problem. This ticket has been created to record the occurrence, allow me to try and reproduce the problem and to be a place holder where other reports of the same problem can be recorded. +Note:+ Cloudbees support were unable to find a problem on their side. Example jenkinsfile (in editor): {code:java} pipeline{ agent{ label 'Win10' } stages{ stage('P4 Sync'){ steps{ script{ def p4 = p4 credential: 'MasterCredential', workspace: manualSpec(charset: 'utf8', name: 'CLIENT', pinHost: false, spec: clientSpec(allwrite: true, backup: false, clobber: false, compress: false, line: 'WIN', locked: false, modtime: false, rmdir: false, streamName: '', type: 'WRITABLE', view: '//depot/... //CLIENT/...')) p4.run("sync","-f", "//depot/PATH/...#0") p4.run("sync","-f", "//depot/PATH/...") } } } } } {code} |
Karl Wirth
made changes -
| Labels | New: P4_VERIFY |
Karl Wirth
made changes -
| Assignee | Original: Karl Wirth [ p4karl ] |
Karl Wirth
made changes -
| Link |
New:
This issue is duplicated by |
Karl Wirth
made changes -
| Rank | New: Ranked higher |
Karl Wirth
made changes -
| Rank | New: Ranked lower |
Paul Allen
made changes -
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Link | New: This issue is blocked by JENKINS-65643 [ JENKINS-65643 ] |
| Link | Original: This issue is blocked by JENKINS-65643 [ JENKINS-65643 ] |
