[JIRA] (JENKINS-62008) Expose P4_CLIENT, P4_USER and P4_PORT as the environment variables P4CLIENT, P4USER and P4PORT for scripts

[kwirth@perforce.com (JIRA)]

Karl Wirth created an issue

Jenkins / JENKINS-62008 Expose P4_CLIENT, P4_USER and P4_PORT as the environment variables P4CLIENT, P4USER and P4PORT for scripts Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2020-04-22 11:54 Environment: 1.10.12 Labels: P4_VERIFY Priority: Minor Reporter: Karl Wirth The old community P4 plugin used to expose the variables P4PORT, P4USER and P4CLIENT as environment variables for scripts to use. The new plugin on purpose uses different variables to ensure we dont override variables that are already set in the environment. Would be good if we had the option to also automatically set P4PORT=P4_PORT, P4USER=P4_USER and P4_CLIENT=P4_CLIENT. Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[DavidRod777@gmail.com (JIRA)]

David Rodriguez updated an issue

Jenkins / JENKINS-62008 Expose P4_CLIENT, P4_USER and P4_PORT as the environment variables P4CLIENT, P4USER and P4PORT for scripts

Change By: David Rodriguez The old community P4 plugin used to expose the variables P4PORT, P4USER and P4CLIENT as environment variables for scripts to use. The new plugin on purpose uses different variables to ensure we dont override variables that are already set in the environment. Would be good if we had the option to also automatically set P4PORT=P4_PORT, P4USER=P4_USER and P4_CLIENT P4CLIENT =P4_CLIENT.

Add Comment

[kwirth@perforce.com (JIRA)]

Karl Wirth commented on JENKINS-62008

Re: Expose P4_CLIENT, P4_USER and P4_PORT as the environment variables P4CLIENT, P4USER and P4PORT for scripts Please see JENKINS-61943 for workarounds.

Add Comment