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

Error message "Depot '${depot}' doesn't exist."

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • p4-plugin
    • None
    • Jenkins 2.289.3
      P4 plug-in 1.11.6

       From “Source Code Management” > “Perforce Software” > “Workspace behavior" > clicking "Streams" > “Stream Codeline” > then I did put same as the above "String Parameter".

      it shows the message “Depot ‘${depot}’ doesn’t exist.”

      However, a build is run okay.

        1. image-1.png
          image-1.png
          121 kB
        2. image-2.png
          image-2.png
          113 kB
        3. image-3.png
          image-3.png
          100 kB
        4. workspace.png
          workspace.png
          141 kB

          [JENKINS-67613] Error message "Depot '${depot}' doesn't exist."

          Karl Wirth added a comment -

          yjang_perforce- What is the workspace name format you are using here? It is important that it includes the variable you have for depot name and stream name to ensure the correct sync_id is used.

          For this I'm changing it to an enhancement request as the GUI does not perform variable expansion on that field.  The request is that we check if a variable is being uses and do not throw up an error if a variable is used.

          Karl Wirth added a comment - yjang_perforce - What is the workspace name format you are using here? It is important that it includes the variable you have for depot name and stream name to ensure the correct sync_id is used. For this I'm changing it to an enhancement request as the GUI does not perform variable expansion on that field.  The request is that we check if a variable is being uses and do not throw up an error if a variable is used.

          Youjeong Jang added a comment -

          p4karl The workspace name format was just set by default and I just used that... Please see the attached.

          Youjeong Jang added a comment - p4karl The workspace name format was just set by default and I just used that... Please see the attached.

          Karl Wirth added a comment -

          Hi yjang_perforce - Thanks. Putting variables in the stream codeline is not recommended (it will break polling) so in this case you need to make sure every workspace is unique per stream that is built. I would suggest you use the workspace name:

           

          jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-${depot}-${folder}
          

          This ensures that when the job runs the sync you dont get artifacts from different streams left in the build workspace from a previous build that used a different stream.

           

          Karl Wirth added a comment - Hi yjang_perforce  - Thanks. Putting variables in the stream codeline is not recommended (it will break polling) so in this case you need to make sure every workspace is unique per stream that is built. I would suggest you use the workspace name:   jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-${depot}-${folder} This ensures that when the job runs the sync you dont get artifacts from different streams left in the build workspace from a previous build that used a different stream.  

            Unassigned Unassigned
            yjang_perforce Youjeong Jang
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: