[
https://issues.jenkins-ci.org/browse/JENKINS-13296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161366#comment-161366
]
SCM/JIRA link daemon commented on JENKINS-13296:
------------------------------------------------
Code changed in jenkins
User: Rob Petti
Path:
src/main/java/hudson/plugins/perforce/PerforceSCM.java
src/test/java/hudson/plugins/perforce/PerforceSCMTest.java
http://jenkins-ci.org/commit/perforce-plugin/0dc62e323624872d0a47c17a3ed268000d6c4374
Log:
[JENKINS-13296] check that non-excluded files are actually in the view before
considering the changelist non-excluded
> Changelists that include excluded files and files outside of the client view
> will trigger a build.
> --------------------------------------------------------------------------------------------------
>
> Key: JENKINS-13296
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13296
> Project: Jenkins
> Issue Type: Improvement
> Components: perforce
> Reporter: Patrick McKeown
> Assignee: Rob Petti
> Priority: Minor
>
> If there is already a way to handle this I apologize, looked around but
> didn't find anything.
> Given a client spec
> //depot/test/... //client/test/...
> with an exclude list such as
> //depot/test/exclude/...
> and polling turned on-
> if someone submits a changelist with an excluded file and a file outside the
> client spec such as
> changelist 1234
> //depot/test/exclude/example.txt#1
> //depot/test2/example2.txt#1
> then //depot/test2/example2.txt#1 will trigger the build as it does not match
> anything in the exclude list.
> I would like a way to consider any files outside of the client spec as
> excluded files without actually having to specify them. Thanks!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
