casz Hi. I'm not sure I fully understand your question. I do want to notify everyone that promoted a change to the package (Package A) of a failed build, but I don't want to notify those who promoted a change to another package (Package B) of a "Package A" failed build - they should only be notified of a "Package B" failed build.

We currently notify a distribution list, with a handful of developers on it, of all build success/failures for all package jobs (using the Jenkins email-ext plugin). What I would like to do is have the changes for a job match the change detection. Currently the changes for a job are all the changes for the stream since the job last ran, not just the changes for the sub-folder since the job last ran. I know not everyone may want this behavior, so to optionally be able to enable this would be fine by me. Does this make sense? I can add a scenario example if that would help.

casz Is this something that may be addressed in a future update, or is this something you are not looking to implement? If you are not looking to implement this, do you have any suggestions for how I may be able to do something similar within the Jenkins job (to prevent changes promoted to folders outside of the build purview from showing in the changeset)? Thanks.

mitorez I have resigned my position as maintainer for the plugin and actively looking for a new maintainer.

https://groups.google.com/forum/#!topic/jenkinsci-dev/DQrkUk8TYFY

Ok, thank you for the update casz

I have not tested this yet, but is this issue resolved by the following bold release note text? Thanks.

Version 0.7.16 (05/15/2018) - Micro Focus Contributed

• It is now possible to enable / disable the AccuRev plugin from interacting with the AccuRev server. This is useful when the AccuRev stream hierarchy is being reworked and you don’t want Jenkins building while this activity is underway.
• Fixed problem with Jenkins reporting "No port number specified for connecting to server" error, when using AccuRev 7.1 or higher.
• Jenkins now correctly works with the "Filter for Poll SCM" option.
• Jenkins user can now validate the connection of configured AccuRev server , using "Test Connection" option.

AccuRev plugin 0.7.16 did not fix this issue.

Changed Priority because this issue prevents accurate reporting of source code changes from an AccuRev promote so we are unable to use our automated issue updater plugin for JIRA. Thanks.

Is there anyway someone from Micro Focus could look into and correct this issue? It really makes it impossible to accurately and programmatically update JIRAs during the build process when the changes for a sub-folder filtered build job show all changes in the stream (regardless of sub-folder) since the last run of the job.

2018-10-15 update:
Micro Focus internal defect RPI #1115588

While a specific fix from AccuRev was never provided to address this issue, several fixes to the plug-in were provided - those fixes in addition to recreating the jobs with some AccuRev filtering changes has provided more consistent results in the job changes report. Closing this issue as clean-up, as it will never be specifically worked on.