|
||||||||
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 |
- [JIRA] (JENKINS-15653) Filter changes by view... bgold...@synopsys.com (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... rob.pe...@gmail.com (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... bgold...@synopsys.com (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... bgold...@synopsys.com (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... rob.pe...@gmail.com (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... bgold...@synopsys.com (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... bgold...@synopsys.com (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... bgold...@synopsys.com (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... rob.pe...@gmail.com (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... bgold...@synopsys.com (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... bgold...@synopsys.com (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... rob.pe...@gmail.com (JIRA)
The plugin already only shows the changesets that contain files that are in the currently defined workspace/view map. So #1, (and by extension #3,) is already implemented...
The file listing for each changeset is provided by perforce itself, and the 'p4 describe' command used does not have the ability to filter that file listing. As you say, ideally perforce would do this filtering for you, but I don't believe there is such a command for doing that... Please let me know if I'm wrong.