I would like to see this option implemented. I believe it would give the user fine tuning when it comes to seeing the set of changes for a given build.
If the user has multiple branch specs defined within the client view map then all changes from the client view are displayed within the changelog. At our company we have hundreds of devs working 24/7 and the change log can become massive.
Example:
Client Workspace View:
//demo/test/sw/01.0/trunk/...
//demo/common_libs/sw/01.0/trunk/...
Add option for "Use View mask Polling:
//demo/test/sw/01.0/trunk/...
Trigger a build if source changes are made to the demo-test-trunk project.
The build will poll and syncs properly. The problem exist that the changelog will show all all the changes from the branch specs listed within the client workspace. We only want to see the changes that triggered the build, i.e. the view mask we are using for polling.
As of right now I'm having to create a separate setup job with a single branch location using the view mask polling and syncing options. I'm then having to sync all the other locations by hand during the build. This allows me to fine tune what's changes are being seen within the changelog. This is a kludgy alternative but works for now.
It would truly be nice to have the option "Use View Mask for ChangeLog" or to be able to exclude branches from the changelog.
Is this difficult to implement?
It would be useful to have this feature as I'm trying to setup Jenkins to build only when the dependencies of a job target change.
Unfortunately the workspace view often contains more files then are necessary to build the target, so I'm intending to auto-generate the dependency list each time a job builds and use it to update the Perforce ViewMask used for polling.
The same ViewMask should be used for the ChangeLog and sending email notifications.