Details
-
Type:
Improvement
-
Status: Open (View Workflow)
-
Priority:
Minor
-
Resolution: Unresolved
-
Component/s: p4-plugin
-
Labels:
-
Environment:1.10.12
-
Similar Issues:
Description
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 P4CLIENT=P4_CLIENT.
Attachments
Issue Links
- causes
-
JENKINS-61943 Jenkins2, P4 Plugin: Error must create client <name>' to access local files
-
- Resolved
-
Activity
Field | Original Value | New Value |
---|---|---|
Description | 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. | 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 P4CLIENT=P4_CLIENT. |
Link |
This issue causes |