[ https://issues.jenkins-ci.org/browse/JENKINS-11369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159292#comment-159292 ]
Rob Petti commented on JENKINS-11369: ------------------------------------- Sounds good to me! You may want to look into a function called "readResolve" for performing the upgrade between versions. The perforce plugin currently doesn't implement it, but the GitSCM plugin has a good example of how this can be used. > 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