Articles in this section

See more

Documentation issue in configuration_reference with P4 definition

Avatar
LeeBenhart
Updated
Follow 

The documentation indicated the following is true of the client name


The client name format is: [hostname]-[pipeline name]-[a random hash code], for example "cruise-myhostname-mypipelinename-wOaJ9kjpfgOLQCncki19ikXt5Q".


However, as I review the workspaces in perforce I see the name as

cruise-[hostname]-[a random hash code], for example

cruise-GOSERVERHOSTNAME-0b67b89b-0553-47f3-8e2b-9d53991f9e5d-GhtlsE2ZthANAijUeoe5n4MuOZU

Comments

3 comments

Sort by Date Votes
  • Avatar
    Santosh Hegde

    Thanks for reporting this. We will fix it.

    0
    Comment actions Permalink
  • Avatar
    LeeBenhart

    Santosh,


    I wanted to clarify. as I did some further looking today.


    I noticed today the documentation seems to describe what the GO_P4_CLIENT environment variable to indicate the perforce client name.


    So in reviewing the GO_P4_CLIENT environment variable, it does not seem to match the documentation, as it is


    cruise-[agent hostname]-[pipelinename]-[random hash]


    'GO_P4_CLIENT_[pipeline]' to value 'cruise-[AGENTHOST]-[PIPELINENAME]-[random hash]'


    however the bigger issue is this does not match the client workspace name in perforce.


    This makes it more of an issue than just documentation.


     


    Lee

    0
    Comment actions Permalink
  • Avatar
    Santosh Hegde

    Hi Lee,


     


    Could you please log this as a support ticket. Please upload the sanitized console log output for the job.


     


    Thanks,


    Santosh

    0
    Comment actions Permalink

Please sign in to leave a comment.