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

Perforce plugin adds wrong environment variable to build environment

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Component/s: perforce-plugin
    • Labels:
      None
    • Environment:
      Hudson 1.339
      Perforce plugin 1.0.16
      Perforce server 2007.2
    • Similar Issues:

      Description

      The Perforce plugin is adding the wrong variable to the build environment. It is adding PCLIENT, not P4CLIENT. Verfied using the following ant file checked into Perforce:

      <project default="env">
        <target name="env">
          <property environment="env" />
          <echoproperties />
        </target>
      </project>
      

      This outputs the following Perforce related variables:

      [echoproperties] env.P4PORT=sealperf01.na.tibco.com\:1666
      [echoproperties] env.P4USER=qpe5
      [echoproperties] env.P4_CHANGELIST=306267
      [echoproperties] env.PCLIENT=autointegrate
      

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              bbassett Brian Bassett
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: