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

No e-mail when using other/template post-build steps

      We have several jobs which share Post-Build Actions.
      All jobs are MultiConfiguration Jobs.

      A main job (Let's call it e.g. MyMainJob) actually acts as a template job.
      The other (secondary) jobs use the Post-Build Actions from MyMainJob.

      1. When the main job build fails e-mail notifications are sent properly. We see info in the console output.
      2. When one of the other (secondary) jobs fails, the e-mail notifications are not sent. Nothing is shown in the console output either.

      Same count for any other e-mail that's supposed to be sent (Fixed, Unstable, ...)

      Relevant configuration of the email-ext is:

      • Fixed Project Recipient List
      • Attach Build Log: _Compress and Attach Build log
      • Trigger for matrix projects: Trigger only parent job
      • Triggers:
        • Failure - 1st (using default config)
        • Failure - Still (using default config)
        • Failure -> Unstable (Test Failures) (using default config)
        • Unstable (Test Failures) - 1st (using default config)
        • Unstable (Test Failures) - Still (using default config)
        • Unstable (Test Failures)/Failure -> Success (using default config)
      • other settings: default config

          [JENKINS-24537] No e-mail when using other/template post-build steps

          Alex Earl added a comment -

          This doesn't apply to email-ext.

          Alex Earl added a comment - This doesn't apply to email-ext.

          This is still an issue with the latest releases:

          • Jenkins 1.596.2
          • Email Extension Plugin 2.40
          • Matrix Project Plugin 1.4.1

          It only applies to the configuration: Trigger only parent job
          When any of the axis Job from the matrix Job fails, I expect an e-mail for the parent Job,
          but that seems not to work.

          When changing to Trigger for each configuration, we correctly get an e-mail for every failing axis build.
          But that is just what we don't want. We want a single e-mail for the (complete) Matrix Job, showing all failing axis builds.

          It seems really an issue related to the combination of the Matrix Project Plugin and Email Extension Plugin.

          Thank you in advance for looking into this!

          Tom Ghyselinck added a comment - This is still an issue with the latest releases: Jenkins 1.596.2 Email Extension Plugin 2.40 Matrix Project Plugin 1.4.1 It only applies to the configuration: Trigger only parent job When any of the axis Job from the matrix Job fails, I expect an e-mail for the parent Job, but that seems not to work. When changing to Trigger for each configuration , we correctly get an e-mail for every failing axis build. But that is just what we don't want. We want a single e-mail for the (complete) Matrix Job, showing all failing axis builds. It seems really an issue related to the combination of the Matrix Project Plugin and Email Extension Plugin . Thank you in advance for looking into this!

          Daniel Beck added a comment -

          Tom: Could you confirm that you're not using Template Project Plugin?

          Daniel Beck added a comment - Tom: Could you confirm that you're not using Template Project Plugin?

          Hi danielbeck,

          Thank you for your quick response!
          It is really appreciated!

          I can't find any "Template Project Plugin" entry in our list of installed plugins.
          Actually is is neither listed in the "available plugins"...

          So, if it is not a part of the Jenkins core, I expect that I'm not using it...

          Tom Ghyselinck added a comment - Hi danielbeck , Thank you for your quick response! It is really appreciated! I can't find any " Template Project Plugin " entry in our list of installed plugins. Actually is is neither listed in the " available plugins "... So, if it is not a part of the Jenkins core, I expect that I'm not using it...

          Alex Earl added a comment -

          @Tom, I don't think you are seeing the same issue then. Please open a new issue.

          Alex Earl added a comment - @Tom, I don't think you are seeing the same issue then. Please open a new issue.

          Hi slide_o_mix,

          This is actually a follow-up for the original issue: When I change
          Trigger for matrix projects: Trigger only parent job
          to
          Trigger for matrix projects: Trigger for each configuration
          it does work as expected.

          I opened a new issue JENKINS-28228

          Tom Ghyselinck added a comment - Hi slide_o_mix , This is actually a follow-up for the original issue: When I change Trigger for matrix projects : Trigger only parent job to Trigger for matrix projects : Trigger for each configuration it does work as expected. I opened a new issue JENKINS-28228

          This may be the same issue, or at least related to it

          Tom Ghyselinck added a comment - This may be the same issue, or at least related to it

          Component has changed, but it looks like the Assignee hasn't been defaulted to the new component.

          I just trigger this because this requires us to do quite some maintenance to avoid floods of e-mails to our developers.

          Thank you very much in advance for looking into it!

          Tom Ghyselinck added a comment - Component has changed, but it looks like the Assignee hasn't been defaulted to the new component. I just trigger this because this requires us to do quite some maintenance to avoid floods of e-mails to our developers. Thank you very much in advance for looking into it!

          Same issue here!

          Tom Ghyselinck added a comment - Same issue here!

          Hi slide_o_mix,

          I just found that an important thing is the Main Job is also a Matrix Job.

          When I have a similar configuration with the Main Job being a FreeStyle Job, then it seems to work.

          Note: In the latter case, I'm not able to define Trigger for matrix projects to either

          • Trigger only parent job
          • or Trigger for each configuration

          It looks like it defaults to the last one.

          ... which explains why it works when I have a FreeStyle project as Main Job

          Tom Ghyselinck added a comment - Hi slide_o_mix , I just found that an important thing is the Main Job is also a Matrix Job . When I have a similar configuration with the Main Job being a FreeStyle Job , then it seems to work. Note : In the latter case, I'm not able to define Trigger for matrix projects to either Trigger only parent job or Trigger for each configuration It looks like it defaults to the last one. ... which explains why it works when I have a FreeStyle project as Main Job

            huybrechts huybrechts
            tom_ghyselinck Tom Ghyselinck
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: