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

"checkout perforce" does not fail on "Syntax error" when "Missing client name and/or owner in spec"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • p4-plugin
    • Jenkins ver. 2.60.3 LTS
      p4-plugin ver. 1.7.5

      Pipeline job configuration with wrong specPath:

       workspace: specFileSpec(
 charset:   'utf8', 
 name:      'master-SPEC', 
 pinHost:   false, 
 specPath:  '//depot/path/to/spec/undefined.p4s')

      Console ouptut:

      [Pipeline] {
[Pipeline] checkout
... p4 client -o master-SPEC +
... p4 info +
... p4 print -q //depot/path/to/spec/undefined.p4s +
Error in client specification.
'client_form-in_check' validation failed: Error detected at line 1.
Syntax error in '//depot/path/to/spec/undefined.p4s'.
Missing client name and/or owner in spec!

      → Should stop here... but continues

      ... p4 client -o master-SPEC +
... p4 client -o master-SPEC +
... p4 client -i +
... client: master-SPEC
... p4 client -o master-SPEC +
... p4 info +
... p4 counter change +
... p4 changes -m1 -ssubmitted //master-SPEC/... +
Building on Node: master
... p4 client -o master-SPEC +
... p4 info +

P4 Task: establishing connection.
...

          [JENKINS-46919] "checkout perforce" does not fail on "Syntax error" when "Missing client name and/or owner in spec"

          Paul Allen added a comment -

          I think this has been resolved, I am unable to reproduce the issue:

          The p4 print detects the error and aborts the build e.g.

          Started by user anonymous
[Pipeline] node
Running on master in /Users/pallen/Workspaces/main.p4-jenkins/public/work/workspace/badPipeline
[Pipeline] {
[Pipeline] checkout
... p4 client -o master-SPEC +
... p4 info +
... p4 print -q //depot/path/to/spec/undefined.p4s -
p4 print -q //depot/path/to/spec/undefined.p4s

//depot/path/to/spec/undefined.p4s - no such file(s).

P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: //depot/path/to/spec/undefined.p4s - no such file(s).

[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: //depot/path/to/spec/undefined.p4s - no such file(s).

Finished: FAILURE

          Paul Allen added a comment - I think this has been resolved, I am unable to reproduce the issue: The p4 print detects the error and aborts the build e.g. Started by user anonymous [Pipeline] node Running on master in /Users/pallen/Workspaces/main.p4-jenkins/ public /work/workspace/badPipeline [Pipeline] { [Pipeline] checkout ... p4 client -o master-SPEC + ... p4 info + ... p4 print -q //depot/path/to/spec/undefined.p4s - p4 print -q //depot/path/to/spec/undefined.p4s //depot/path/to/spec/undefined.p4s - no such file(s). P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: //depot/path/to/spec/undefined.p4s - no such file(s). [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: //depot/path/to/spec/undefined.p4s - no such file(s). Finished: FAILURE

          Paul Allen added a comment -

          Unable to reproduce as of 1.8.7

          Paul Allen added a comment - Unable to reproduce as of 1.8.7

            p4paul Paul Allen
            rolegic Ronan Le Gallic
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: