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

Post-build from other project: No e-mail send for "Trigger only parent job"

      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.
      The other (secondary) jobs use the Post-Build Actions from MyMainJob.

      We want a single e-mail to be sent for the MultiConfiguration Jobs, including build logs for all failing matrix configurations. Therefor we configured the Email Extension Plugin with * Trigger for matrix projects: Trigger only parent job.

      1. When (one of the matrix configurations of) the main job build fails a single e-mail notification is sent properly. We also see this info in the console output of MyMainJob.
      2. When (one of the matrix configurations of) the secondary jobs fails, the e-mail notification is 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:
        • Aborted (using default config)
        • 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

      When we change the config to * Trigger for matrix projects: Trigger for each configuration, the e-mail notifications are sent correctly for every matrix configuration.
      We see the info at the console output of the matrix configurations' builds, both for the main job and the secondary jobs.

      This is quite important since we have large matrix projects and a build failure causes an e-mail flood for the developers.

          [JENKINS-28228] Post-build from other project: No e-mail send for "Trigger only parent job"

          Oh, my excuses if this is confusing!

          I just mean that our secondary jobs are using build steps and post-build steps_ from the main job.
          So that the main job is acting as some kind of template configuration for the secondary jobs.

          I hope this clears up things a bit!

          Tom Ghyselinck added a comment - Oh, my excuses if this is confusing! I just mean that our secondary jobs are using build steps and post-build steps_ from the main job . So that the main job is acting as some kind of template configuration for the secondary jobs . I hope this clears up things a bit!

          Daniel Beck added a comment -

          How is 'main job' involved here other than telling you how 'secondary job' needs to be (manually) configured? If I understand this correctly, the description loses nothing if you don't even mention this.

          Daniel Beck added a comment - How is 'main job' involved here other than telling you how 'secondary job' needs to be (manually) configured? If I understand this correctly, the description loses nothing if you don't even mention this.

          Alex Earl added a comment -

          I think he's just describing how a multiconfig job works. There is a main config and child configurations.

          Alex Earl added a comment - I think he's just describing how a multiconfig job works. There is a main config and child configurations.

          Hi guys,

          Just to the point:

          • main job is a simple multi-configuration job.
          • secondary job is also a simple multi-configuration job, using the build steps and post-build steps from main job

          P.S. Again, my excuses for the confusion!

          Tom Ghyselinck added a comment - Hi guys, Just to the point: main job is a simple multi-configuration job. secondary job is also a simple multi-configuration job, using the build steps and post-build steps from main job P.S. Again, my excuses for the confusion!

          Alex Earl added a comment -

          How is it "using the build steps and post-build steps from main job"? That is my point of confusion.

          Alex Earl added a comment - How is it "using the build steps and post-build steps from main job"? That is my point of confusion.

          Ok, now I get the confusion:

          In the secondary job configuration, we have:

          1. a Build step:
            • Use builders from another project
              • Template Project: main job
          2. a Post-build Action
            • Use publishers from another project
              • Template Project: main job

          Hmm, does the Template Project name refer to the Template Project Plugin then?
          Why can't I find any note of it in may installed plugins list then...

          Tom Ghyselinck added a comment - Ok, now I get the confusion: In the secondary job configuration, we have: a Build step : Use builders from another project Template Project: main job a Post-build Action Use publishers from another project Template Project: main job Hmm, does the Template Project name refer to the Template Project Plugin then? Why can't I find any note of it in may installed plugins list then...

          Tom Ghyselinck added a comment - - edited

          Ha! found it:

          In http://<jenkins_url>/systemInfo:

          Name Version Enabled Pinned
          template-project	1.4.2	true	false
          

          Tom Ghyselinck added a comment - - edited Ha! found it: In http://<jenkins_url>/systemInfo : Name Version Enabled Pinned template-project 1.4.2 true false

          Alex Earl added a comment -

          Ok, so if the template project is enabled, then my comment on the other issue stands, the Template Project Plugin doesn't implement the correct functionality for this to work.

          Alex Earl added a comment - Ok, so if the template project is enabled, then my comment on the other issue stands, the Template Project Plugin doesn't implement the correct functionality for this to work.

          Daniel Beck added a comment -

          Now that we know that Tom is actually using Template Project, this is a duplicate of JENKINS-28228.

          Daniel Beck added a comment - Now that we know that Tom is actually using Template Project, this is a duplicate of JENKINS-28228 .

          I suppose you mean duplicate of JENKINS-24537?

          Thank you very much for helping to clear this out!

          Tom Ghyselinck added a comment - I suppose you mean duplicate of JENKINS-24537 ? Thank you very much for helping to clear this out!

            slide_o_mix Alex Earl
            tom_ghyselinck Tom Ghyselinck
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: