[JIRA] (JENKINS-46919) "checkout perforce" does not fail on "Syntax error" when "Missing client name and/or owner in spec"
Title: Message Title Paul Allen closed an issue as Cannot Reproduce Unable to reproduce as of 1.8.7 Jenkins / JENKINS-46919 "checkout perforce" does not fail on "Syntax error" when "Missing client name and/or owner in spec" Change By: Paul Allen Status: In Progress Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-46919) "checkout perforce" does not fail on "Syntax error" when "Missing client name and/or owner in spec"
Title: Message Title Paul Allen started work on JENKINS-46919 Change By: Paul Allen Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46919) "checkout perforce" does not fail on "Syntax error" when "Missing client name and/or owner in spec"
Title: Message Title
Paul Allen commented on JENKINS-46919
Re: "checkout perforce" does not fail on "Syntax error" when "Missing client name and/or owner in spec"
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
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
[JIRA] (JENKINS-46919) "checkout perforce" does not fail on "Syntax error" when "Missing client name and/or owner in spec"
Title: Message Title Paul Allen assigned an issue to Paul Allen Jenkins / JENKINS-46919 "checkout perforce" does not fail on "Syntax error" when "Missing client name and/or owner in spec" Change By: Paul Allen Assignee: Paul Allen Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46919) "checkout perforce" does not fail on "Syntax error" when "Missing client name and/or owner in spec"
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-46919 "checkout perforce" does not fail on "Syntax error" when "Missing client name and/or owner in spec" Change By: Paul Allen Labels: P4_B Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
