Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-16637

problems exposing P4CLIENT and P4PASSWD to env

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • p4-plugin
    • None
    • Windows

      If the environment variable is assigned a value before the Jenkins slave starts the value is not changed by the plugin.
      The P4CLIENT problem is visible, when a system level P4CLIENT is defined and the slave is run as a service as a user (MYDOMAIN\BUILDUSER) not as SYSTEM. If the build now uses this slave, perforce plugin cannot override P4CLIENT variable.

          [JENKINS-16637] problems exposing P4CLIENT and P4PASSWD to env

          Markus Strand created issue -
          Rob Petti made changes -
          Assignee Original: Rob Petti [ rpetti ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 147461 ] New: JNJira + In-Review [ 176908 ]
          Jenkins IRC Bot made changes -
          Component/s New: p4-plugin [ 19224 ]
          Component/s Original: perforce-plugin [ 15506 ]

            Unassigned Unassigned
            strand Markus Strand
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: