[JIRA] (JENKINS-5120) Support node-specific Perforce configuration

[jclausen@505games.com (JIRA)]

Josh Clausen commented on JENKINS-5120

Re: Support node-specific Perforce configuration I have the same use case: multiple locations, each of which has its own p4 proxy (different IPs in every location). Right now, the plugin clobbers P4HOST and P4PORT, rather than first checking if there are any existing environment variables by those names. So, that would be my recommendation - use any already-set environment variables rather than clobbering those environment variables with whatever happens to be in the form for the credential. Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[rob.petti@gmail.com (JIRA)]

Rob Petti closed an issue as Won't Do

This ticket looks like it was made against the perforce-plugin before it was deprecated, and was erroneously moved to p4-plugin. Perforce-plugin is no longer being maintained and has been decommissioned. If you are having this issue with the p4-plugin, I recommend opening a new ticket with as much detail as possible so they can resolve the issue. Jenkins / JENKINS-5120 Support node-specific Perforce configuration Change By: Rob Petti Status: Open Closed Resolution: Won't Do

Add Comment