[JENKINS-64707] [P4 Plugin] P4_ROOT is not set properly - pointing to build workspace instead of p4 client root - Jenkins Jira

Type: Bug
Resolution: Unresolved
Priority: Minor
Component/s: p4-plugin
Labels:
Environment:
Jenkins 2.276 (Windows)
P4 Plugin 1.11.2

Similar Issues:
Powered by SuggestiMate

Show

The following problem was observed in a pipeline type job:

After the perforce scm step is executed the P4_ROOT environment variable is not set properly. It is pointing to the build workspace instead of the p4 client root of the client used during the scm step. I have tested it using static workspace behavior and the p4 preview option. Basically the P4_ROOT is the same as WORKSPACE environment variable, but it should be set to p4 clients root.

agent{
  node{
      label "node1"
      customWorkspace "C:\\Custom\\BuildWorkspacePath"
  }
}
stages{
  stage('Test'){
    steps{
      // Perforce client myP4Client has p4 root set to C:\\myP4Client
      checkout perforce(credential: 'myP4Creds', populate: previewOnly(quiet: true), workspace: staticSpec(charset: 'none', name: 'myP4Client', pinHost: false))
      // P4_ROOT will be set to "C:\\Custom\\BuildWorkspacePath" instead of "C:\\myP4Client"
      echo "${currentBuild.rawBuild.getEnvironment()}"
    }
  }
}

is caused by

JENKINS-47005 Let user specify p4 workspace root in manual config

Open

Piotr Ławniczuk created issue - 2021-01-25 14:36

Piotr Ławniczuk made changes - 2021-01-25 14:38

Labels

New: P4_ROOT

Piotr Ławniczuk made changes - 2021-01-25 14:38

Labels

Original: P4_ROOT

New: EnvironmentalVariable P4_ROOT

Piotr Ławniczuk made changes - 2021-01-25 14:38

Labels

Original: EnvironmentalVariable P4_ROOT

New: EnvironmentalVariable P4_ROOT environment-variables

Piotr Ławniczuk made changes - 2021-01-25 14:40

Description

New: The following problem was observed in a pipeline type job:

After the perforce scm step is executed the P4_ROOT environment variable is not set properly. It is pointing to the build workspace instead of the p4 client root of the client used during the scm step. I have tested it using static workspace behavior and the p4 preview option. Basically the P4_ROOT is the same as WORKSPACE environment variable, but it should be set to p4 clients root.

{code:java}
    agent{
        node{
            label "master"
        }
    }
    parameters{
        string (name: 'change', defaultValue: '', trim: true, description: '')
        string (name: 'shelve', defaultValue: '', trim: true, description: '')
    }
    options{
        buildDiscarder logRotator(numToKeepStr: '5')
        timestamps()
    }
    stages{
        stage('first'){
            steps{
                checkout perforce(credential: 'robot.obibok_1777', populate: previewOnly(quiet: true), workspace: staticSpec(charset: 'none', name: 'robot.obibok_IDK300_TESTSTREAM_development', pinHost: false))
                echo "${currentBuild.rawBuild.getEnvironment()}"
                setupPipeline(displayName: "test", description: "PS4")
            }
        }
    }
}
{code}

Piotr Ławniczuk made changes - 2021-01-25 14:44

Description

Original: The following problem was observed in a pipeline type job:

After the perforce scm step is executed the P4_ROOT environment variable is not set properly. It is pointing to the build workspace instead of the p4 client root of the client used during the scm step. I have tested it using static workspace behavior and the p4 preview option. Basically the P4_ROOT is the same as WORKSPACE environment variable, but it should be set to p4 clients root.

{code:java}
    agent{
        node{
            label "master"
        }
    }
    parameters{
        string (name: 'change', defaultValue: '', trim: true, description: '')
        string (name: 'shelve', defaultValue: '', trim: true, description: '')
    }
    options{
        buildDiscarder logRotator(numToKeepStr: '5')
        timestamps()
    }
    stages{
        stage('first'){
            steps{
                checkout perforce(credential: 'robot.obibok_1777', populate: previewOnly(quiet: true), workspace: staticSpec(charset: 'none', name: 'robot.obibok_IDK300_TESTSTREAM_development', pinHost: false))
                echo "${currentBuild.rawBuild.getEnvironment()}"
                setupPipeline(displayName: "test", description: "PS4")
            }
        }
    }
}
{code}

New: The following problem was observed in a pipeline type job:

After the perforce scm step is executed the P4_ROOT environment variable is not set properly. It is pointing to the build workspace instead of the p4 client root of the client used during the scm step. I have tested it using static workspace behavior and the p4 preview option. Basically the P4_ROOT is the same as WORKSPACE environment variable, but it should be set to p4 clients root.

{code:java}
agent{
  node{
      label "node1"
      customWorkspace "C:\\Custom\\BuildWorkspacePath"
  }
}
stages{
  stage('Test'){
    steps{
        // Perforce client myP4Client has p4 root set to C:\\myP4Client
        checkout perforce(credential: 'myP4Creds', populate: previewOnly(quiet: true), workspace: staticSpec(charset: 'none', name: 'myP4Client', pinHost: false))
        // P4_ROOT will be set to "C:\\Custom\\BuildWorkspacePath" instead of "C:\\myP4Client"
        echo "${currentBuild.rawBuild.getEnvironment()}"
    }
  }
}

{code}

Piotr Ławniczuk made changes - 2021-01-25 14:45

Description

Original: The following problem was observed in a pipeline type job:

After the perforce scm step is executed the P4_ROOT environment variable is not set properly. It is pointing to the build workspace instead of the p4 client root of the client used during the scm step. I have tested it using static workspace behavior and the p4 preview option. Basically the P4_ROOT is the same as WORKSPACE environment variable, but it should be set to p4 clients root.

{code:java}
agent{
  node{
      label "node1"
      customWorkspace "C:\\Custom\\BuildWorkspacePath"
  }
}
stages{
  stage('Test'){
    steps{
        // Perforce client myP4Client has p4 root set to C:\\myP4Client
        checkout perforce(credential: 'myP4Creds', populate: previewOnly(quiet: true), workspace: staticSpec(charset: 'none', name: 'myP4Client', pinHost: false))
        // P4_ROOT will be set to "C:\\Custom\\BuildWorkspacePath" instead of "C:\\myP4Client"
        echo "${currentBuild.rawBuild.getEnvironment()}"
    }
  }
}

{code}

New: The following problem was observed in a pipeline type job:

After the perforce scm step is executed the P4_ROOT environment variable is not set properly. It is pointing to the build workspace instead of the p4 client root of the client used during the scm step. I have tested it using static workspace behavior and the p4 preview option. Basically the P4_ROOT is the same as WORKSPACE environment variable, but it should be set to p4 clients root.

{code:java}
agent{
  node{
      label "node1"
      customWorkspace "C:\\Custom\\BuildWorkspacePath"
  }
}
stages{
  stage('Test'){
    steps{
      // Perforce client myP4Client has p4 root set to C:\\myP4Client
      checkout perforce(credential: 'myP4Creds', populate: previewOnly(quiet: true), workspace: staticSpec(charset: 'none', name: 'myP4Client', pinHost: false))
      // P4_ROOT will be set to "C:\\Custom\\BuildWorkspacePath" instead of "C:\\myP4Client"
      echo "${currentBuild.rawBuild.getEnvironment()}"
    }
  }
}

{code}

Karl Wirth made changes - 2021-01-27 10:26

Link

New: This issue is caused by JENKINS-47005 [ JENKINS-47005 ]

Karl Wirth made changes - 2021-02-23 16:26

Resolution		New: Fixed [ 1 ]
Status	Original: Open [ 1 ]	New: Closed [ 6 ]

Karl Wirth made changes - 2022-11-10 16:10

Resolution	Original: Fixed [ 1 ]
Status	Original: Closed [ 6 ]	New: Reopened [ 4 ]

Karl Wirth made changes - 2022-11-10 16:10

Labels

Original: EnvironmentalVariable P4_ROOT environment-variables

New: EnvironmentalVariable P4_A P4_ROOT P4_VERIFY environment-variables

Assignee:: Unassigned

Reporter:: Piotr Ławniczuk

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2021-01-25 14:36

Updated:: 2022-11-10 16:10

Jenkins

Details

Description

Attachments

Issue Links

Activity

[JENKINS-64707] [P4 Plugin] P4_ROOT is not set properly - pointing to build workspace instead of p4 client root

People

Dates