Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-41102

Job "Changes" do not match "Filter for Poll SCM"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: Major Major
    • accurev-plugin
    • Windows Server 2012 R2
      AccuRev 6.2.3
      Jenkins 2.32.1
      AccuRev Plugin 0.7.6

      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!

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

          Timothy Williams created issue -
          Balaji wanole made changes -
          Assignee Original: Joseph Petersen (old) [ casz ] New: Sneha More [ snehamore ]

          Joseph Petersen (old) added a comment -

          mitorez 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?

          Joseph Petersen (old) added a comment - mitorez 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?
          Joseph Petersen (old) made changes -
          Assignee Original: Sneha More [ snehamore ] New: Joseph Petersen (old) [ casz ]

          Timothy Williams added a comment -

          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.

          Timothy Williams added a comment - 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.
          Timothy Williams made changes -
          Link New: This issue relates to JENKINS-41526 [ JENKINS-41526 ]
          Timothy Williams made changes -
          Link New: This issue relates to JENKINS-42939 [ JENKINS-42939 ]

          Timothy Williams added a comment -

          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.

          Timothy Williams added a comment - 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.

          Joseph Petersen (old) added a comment -

          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

          Joseph Petersen (old) added a comment - 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
          Joseph Petersen (old) made changes -
          Assignee Original: Joseph Petersen (old) [ casz ]

            Unassigned Unassigned
            mitorez Timothy Williams
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: