[JIRA] (JENKINS-58504) P4 Plugin tries to make depot location of Jenkinsfile available regardless of SCM type

[aal...@ea.com (JIRA)]

Title: Message Title

Aaron Ling created an issue   Jenkins / JENKINS-58504 P4 Plugin tries to make depot location of Jenkinsfile available regardless of SCM type Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2019-07-15 23:53 Environment: Jenkins ver. 2.176.1 P4 Plugin v 1.10.2 Priority: Minor Reporter: Aaron Ling https://github.com/jenkinsci/p4-plugin/blob/master/src/main/java/org/jenkinsci/plugins/p4/PerforceScm.java#L545 This code was added to address JENKINS-39107. We have a use-case where our jobs use lightweight checkout to load build scripts from gitlab, but the Jenkinsfiles themselves checkout from p4 to get the actual code that we build. The added code then tries to run 'p4 where' on the Jenkinsfile, but it doesn't exist in p4. This doesn't cause any build failures, but does print the following message: 16:26:55 (p4):cmd:... p4 where E:\workspace\folder\to\Jenkinsfile.groovy 16:26:55 p4 where E:\workspace\folder\to\Jenkinsfile.groovy 16:26:55 E:\workspace\folder\to\Jenkinsfile.groovy - file(s) not in client view.  which causes our failure tracking to erroneously pick it up (because it's a legitimate failure at times in other cases). Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200647.1563234801000.11575.1563234840089%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.