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

"Include Culprits" definition wrong for Still-Unstable trigger

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • email-ext-plugin
    • None

      I'm using the ext-email plugin.

      Person P commits a change that causes the build number A to become unstable (i.e. breaks some tests). I have configured Hudson to email P by specifying an "Unstable" trigger and selecting "Send To Committers".

      Person Q subsequently commits an unrelated change, so build number A+1 will still be unstable. I have configured an "Still Unstable" trigger and selected "Send To Committers" and also "Include Culprits". I expected that Hudson would email both P and Q, however it only emails Q.

      Reading the help text for "Include Culprits", it says "emails will include everyone who committed since the last successful build". In Hudson terminology (as I understand it), successful means either stable or unstable (but not failed). So what the ext-email plugin is doing matches the help text, but it's not the right thing to do. Should "Include Culprits" should email everyone who committed since the last *stable* build.

            Unassigned Unassigned
            mwebber Matthew Webber
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: