-
Bug
-
Resolution: Fixed
-
Critical
-
Operating System:
* Build Slave is Win10 64
* Jenkins master: CentOS: 7.5 64
JDKs:
* Build Slave: Oracle 1.8.0_171
* Master: Oracle 1.8.0_212
Versions:
* Jenkins: 2.164.2
* P4 Plugin: 1.10.3
Jenkins NOT run via container
Jenkins NOT setup via reverse proxy
Jenkins installed with yum (rpm)
Jenkins slave installed via jnlp but running as a serviceOperating System: * Build Slave is Win10 64 * Jenkins master: CentOS: 7.5 64 JDKs: * Build Slave: Oracle 1.8.0_171 * Master: Oracle 1.8.0_212 Versions: * Jenkins: 2.164.2 * P4 Plugin: 1.10.3 Jenkins NOT run via container Jenkins NOT setup via reverse proxy Jenkins installed with yum (rpm) Jenkins slave installed via jnlp but running as a service
After updating from 1.10.0 to 1.10.3 I am seeing the following errors on Windows build slaves:
15:00:01 ERROR: P4: Task Exception: com.perforce.p4java.exception.P4JavaException: com.perforce.p4java.exception.P4JavaException: hudson.AbortException: P4JAVA: Error(s): 15:00:01 symlink file <some symlink> can't be sync'd or created with this client program.
Note that we are using a virtual stream.
- is related to
-
JENKINS-59611 Symlink target update fails when "noclobber" set
-
- Closed
-
[JENKINS-59213] P4 Plugin - Errors when syncing symlinks
Labels | Original: p4-plugin symlink | New: P4_SUPPORT p4-plugin symlink |
Assignee | New: Karl Wirth [ p4karl ] |
Link |
New:
This issue is related to |
Assignee | Original: Karl Wirth [ p4karl ] | New: Charusheela Bopardikar [ cbopardikar ] |
Labels | Original: P4_SUPPORT p4-plugin symlink | New: P4_VERIFY p4-plugin symlink |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |