|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I see. Yup - I definitely thought you meant the spec area in Jenkins for the exclude paths.![]()
There are no replacements in any of the Workspace specs that I've setup. One of them has a few eliminated mappings: -//apath/item/... and it looks like all of them have at least one quoted mapping "//a path/item/..." The mappings all also include files from more than one depot.
The mappings in 95% of the builds exhibiting the problem look like this:
//depot/item/item/... //SpecName/...
"//depot2/path item/item1/..." "//SpecName/path item/item1/..."
//depot2/path2/item2/... //SpecName/path2/item2/...
I think those are the only slightly unusual thing that I have going on. Maybe this is helpful... It's files in the second depot that I'm excluding. However, I'm also making other checkins in that second depot that I would think would trigger the build, because they're not being excluded. The plugin appears to be determining them to be excluded anyway.