[JIRA] (JENKINS-41102) Job "Changes" do not match "Filter for Poll SCM"

13 views
Skip to first unread message

zerotim@gmail.com (JIRA)

unread,
Jan 16, 2017, 9:24:01 AM1/16/17
to jenkinsc...@googlegroups.com
Timothy Williams created an issue
 
Jenkins / Bug JENKINS-41102
Job "Changes" do not match "Filter for Poll SCM"
Issue Type: Bug Bug
Assignee: Joseph Petersen
Components: accurev-plugin
Created: 2017/Jan/16 2:23 PM
Environment: Windows Server 2012 R2
AccuRev 6.2.3
Jenkins 2.32.1
AccuRev Plugin 0.7.6
Labels: scm user-experience
Priority: Minor Minor
Reporter: Timothy Williams

The "Changes" list on my Jenkins jobs (and corresponding emails) using the AccuRev plugin do not match the change detection of the job's "Filter for Poll SCM". Promotes to only the specified sub-folder defined in "Filter for Poll SCM" are correctly identified and kick-off the job, but the "Changes" list for the job that gets kicked-off are all changes for the entire stream since the job last ran, not just the changes for the sub-folder specified in "Filter for Poll SCM".

My stream contains many sub-folders for each "package", and a Jenkins job exists for each "package" sub-folder. With the current behavior, irrelevant change-sets are being sent in job notification emails and developers not involved with the changes of a specific "package" job are being notified about success and failures even though they didn't promote changes to said "package". Is there anyway to make the job "Changes" list match on the changes based on "Filter for Poll SCM"? Thanks!

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

balaji_wanole@yahoo.in (JIRA)

unread,
Jan 16, 2017, 9:32:15 AM1/16/17
to jenkinsc...@googlegroups.com
Balaji wanole assigned an issue to Sneha More
Change By: Balaji wanole
Assignee: Joseph Petersen Sneha More

josephp90@gmail.com (JIRA)

unread,
Jan 16, 2017, 10:28:01 AM1/16/17
to jenkinsc...@googlegroups.com
Joseph Petersen commented on Bug JENKINS-41102
 
Re: Job "Changes" do not match "Filter for Poll SCM"

Timothy Williams Good to see you got the Jenkins Master and Plugin updated

This is totally doable but what if something in the filtered breaks the build? Would it not be better to notify everyone in the changeset?

josephp90@gmail.com (JIRA)

unread,
Jan 16, 2017, 10:29:01 AM1/16/17
to jenkinsc...@googlegroups.com
Joseph Petersen assigned an issue to Joseph Petersen
 
Change By: Joseph Petersen
Assignee: Sneha More Joseph Petersen

zerotim@gmail.com (JIRA)

unread,
Jan 16, 2017, 1:09:01 PM1/16/17
to jenkinsc...@googlegroups.com
Timothy Williams commented on Bug JENKINS-41102
 
Re: Job "Changes" do not match "Filter for Poll SCM"

Joseph Petersen 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.

zerotim@gmail.com (JIRA)

unread,
May 8, 2018, 11:13:02 AM5/8/18
to jenkinsc...@googlegroups.com

Joseph Petersen 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.

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

josephp90@gmail.com (JIRA)

unread,
May 8, 2018, 1:29:02 PM5/8/18
to jenkinsc...@googlegroups.com

Timothy Williams 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

josephp90@gmail.com (JIRA)

unread,
May 8, 2018, 1:32:06 PM5/8/18
to jenkinsc...@googlegroups.com
Joseph Petersen assigned an issue to Unassigned
 
Change By: Joseph Petersen
Assignee: Joseph Petersen

zerotim@gmail.com (JIRA)

unread,
May 8, 2018, 2:39:04 PM5/8/18
to jenkinsc...@googlegroups.com

zerotim@gmail.com (JIRA)

unread,
May 18, 2018, 4:18:02 PM5/18/18
to jenkinsc...@googlegroups.com

I have not tested this yet, but is this issue resolved by the following bolded 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.

zerotim@gmail.com (JIRA)

unread,
May 18, 2018, 4:20:02 PM5/18/18
to jenkinsc...@googlegroups.com
Timothy Williams edited a comment on Bug JENKINS-41102
I have not tested this yet, but is this issue resolved by the following bolded bold [release note text|https://wiki.jenkins.io/display/JENKINS/AccuRev+Plugin]? Thanks.

{quote}
{color:red}Version 0.7.16 (05/15/2018) - Micro Focus Contributed{color}
* 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.
{quote}

zerotim@gmail.com (JIRA)

unread,
May 22, 2018, 11:26:04 PM5/22/18
to jenkinsc...@googlegroups.com

AccuRev plugin 0.7.16 did not fix this issue.

zerotim@gmail.com (JIRA)

unread,
Jun 7, 2018, 10:49:02 AM6/7/18
to jenkinsc...@googlegroups.com
Timothy Williams updated an 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.

Change By: Timothy Williams
Priority: Minor Major

zerotim@gmail.com (JIRA)

unread,
Sep 21, 2018, 10:25:03 AM9/21/18
to jenkinsc...@googlegroups.com
 
Re: Job "Changes" do not match "Filter for Poll SCM"

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.

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

zerotim@gmail.com (JIRA)

unread,
Feb 13, 2019, 10:47:03 AM2/13/19
to jenkinsc...@googlegroups.com
Timothy Williams edited a comment on Bug JENKINS-41102
* 15/Oct/ 2018 -10-15 update:*
Micro Focus internal defect RPI #1115588

zerotim@gmail.com (JIRA)

unread,
Feb 13, 2019, 10:47:03 AM2/13/19
to jenkinsc...@googlegroups.com

15/Oct/2018 update:


Micro Focus internal defect RPI #1115588

zerotim@gmail.com (JIRA)

unread,
Apr 3, 2020, 1:27:03 PM4/3/20
to jenkinsc...@googlegroups.com
Timothy Williams closed an issue as Incomplete
 

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.

Change By: Timothy Williams
Status: Open Closed
Resolution: Incomplete
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages