-
New Feature
-
Resolution: Won't Do
-
Minor
-
None
(This is sort of related to JENKINS-2947, but doesn't really belong there.)
The Perforce configuration for a job doesn't provide much flexibility if you want to run a job on various slaves.
The path to the executable means that the job becomes fixed to an OS (more or less), and doesn't allow for slaves configured with Perforce in a different location.
The P4PORT setting is also a problem (for me). We have slaves that run in various locations, each of which may have their own local p4 proxy which would be optimal. As it stands now, we have to choose one server that is the best compromise for all locations.
- depends on
-
JENKINS-2947 Perforce should factor out global configuration to the global page
-
- Open
-
- is related to
-
-
- Resolved
-
[JENKINS-5120] Support node-specific Perforce configuration
oeuftete
created issue -
| Assignee | New: Rob Petti [ rpetti ] |
| Assignee | Original: Rob Petti [ rpetti ] |
| Link | New: This issue depends on JENKINS-2947 [ JENKINS-2947 ] |
| Link |
New:
This issue is blocking |
| Link |
Original:
This issue is blocking |
| Link |
New:
This issue is related to |
| Workflow | Original: JNJira [ 135204 ] | New: JNJira + In-Review [ 174270 ] |
Jenkins IRC Bot
made changes -
| Component/s | New: p4-plugin [ 19224 ] | |
| Component/s | Original: perforce-plugin [ 15506 ] |
| Resolution | New: Won't Do [ 10001 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |