To me, it looks like the easiest way to support this would be for the plugin to support using existing environment variables. P4PORT, P4USER, and P4PASSWD could be used from the environment if left empty in the job configuration. Make up an environment variable name for the application path, maybe? I don't know.

You can actually leave the path to p4 blank, and it will just use the PATH, I believe. I find that we rarely have to specify it explicitly (and in fact this will be going away entirely when the p4java version is completed)

A work-around for your issue would be to make the hostname:port for the proxies the same at all sites. If you can't set that up (hostname collisions etc.), then you can edit the 'hosts' file on the slaves to create a hostname that resolves to the appropriate server for each machine, then as long as you set up the port numbers to be the same on every proxy, then you should be good.

I think JENKINS-2947 is actually a good solution if we also allow node-level overrides for globally defined perforce servers. It would take quite a bit of work though, so don't expect a solution anytime soon. See what you can do about making your setup a bit more consistent across the board in the meantime.

I appreciate the workaround suggestions, although I don't think that's within the scope of this ticket.

I just want the plugin to be better, so I opened the ticket. If I need workarounds, I'll go to the users list.

Fair enough. I was just trying to help with your immediate problem while I work on the ticket.

Unassigning due to time constraints on my end. If someone else wants to work on this, be my guest.

Leaving the p4 path does not work. Is there a environment variable I can set per node that will work? leaving it blank leaves the command blank even though p4 is in my path.

Sorry, set it to "p4" rather than leave it blank.

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.

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.