[
https://issues.jenkins-ci.org/browse/JENKINS-11369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159271#comment-159271
]
Mikko Tapaninen commented on JENKINS-11369:
-------------------------------------------
I'm working on this one and I'll create a pull request once ready. I would
remove p4 executable path setting from the job level and have it as a tool
installation. As a migration path I was thinking to add a tool installation for
each different p4 executable path that are being used (case insensitive for
Windows). No matter whether the job is enabled or not and whether it's tied on
master or slave. Correct tool installation would then be picked for each job.
There could be some extra unneeded tool installations but I think it's fair
enough. Comments?
> Use ToolInstallation as replacement to p4 path specified in Jobs
> ----------------------------------------------------------------
>
> Key: JENKINS-11369
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11369
> Project: Jenkins
> Issue Type: Improvement
> Components: perforce
> Reporter: Nicolas De Loof
> Assignee: Rob Petti
> Priority: Minor
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
