-
Improvement
-
Resolution: Fixed
-
Minor
-
None
Got this issue :
job is configured with p4 path on build slave /usr/bin/p4. When tagging a build, an error occurred because executing on master that don't have p4 installed on same path.
perforce plugin should use the Jenkins concept of ToolInstallation + NodeSpecific, so that it gets simpler to manage differences between nodes.
- is related to
-
JENKINS-5120 Support node-specific Perforce configuration
-
- Closed
-
-
JENKINS-2947 Perforce should factor out global configuration to the global page
-
- Open
-
[JENKINS-11369] Use ToolInstallation as replacement to p4 path specified in Jobs
Link |
New:
This issue depends on |
Link | New: This issue depends on JENKINS-2947 [ JENKINS-2947 ] |
Assignee | New: Rob Petti [ rpetti ] |
Link |
Original:
This issue depends on |
Link | Original: This issue depends on JENKINS-2947 [ JENKINS-2947 ] |
Link |
New:
This issue is related to |
Link | New: This issue is related to JENKINS-2947 [ JENKINS-2947 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 141595 ] | New: JNJira + In-Review [ 189706 ] |
Component/s | New: p4-plugin [ 19224 ] | |
Component/s | Original: perforce-plugin [ 15506 ] |