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

Mails with build failure reports misses content for maven job type

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • maven-plugin
    • None
    • Jenkins 1.609.3, Maven Integration 2.11, Email Extension 2.40.5

      We use Maven build jobs and in a case of a build failure send a mail with the email-ext plugin.
      With the default template ${SCRIPT, template="groovy-text.template"} the mail contains the last 100 lines of the build log.
      In cases of missing or wrong maven dependencies the mail ends always with <===[JENKINS REMOTING CAPACITY]===>

      The important error information is missing, but are shown in the console log via the web interface.
      For example:

      [INFO] Resolving dependencies of MavenProject: xxx
      [INFO] {osgi.ws=win32, osgi.os=win32, osgi.arch=x86_64, org.eclipse.update.install.features=true}
      [ERROR] Cannot resolve project dependencies:
      [ERROR] Software being installed: ...
      [ERROR] Missing requirement: ....
      

      The build log should be fixed to contain also this kind of information.

          [JENKINS-31857] Mails with build failure reports misses content for maven job type

          Alex Earl added a comment -

          Is "<===[JENKINS REMOTING CAPACITY]===>" in the log anywhere? I call into core for the log, so there really isn't anything I can do in the plugin if core doesn't give me the correct information.

          Alex Earl added a comment - Is "<=== [JENKINS REMOTING CAPACITY] ===>" in the log anywhere? I call into core for the log, so there really isn't anything I can do in the plugin if core doesn't give me the correct information.

          Carsten Kuhl added a comment - - edited

          Yes the string "<===[JENKINS REMOTING CAPACITY]===>" is in the console log.
          But it seems that core doesn't provide the information, because the build object which I can access with the script simple doesn't contain it.
          In the log you see:
          <===[JENKINS REMOTING CAPACITY]===>channel started
          The error mail ends with:
          <===[JENKINS REMOTING CAPACITY]===>

          Carsten Kuhl added a comment - - edited Yes the string "<=== [JENKINS REMOTING CAPACITY] ===>" is in the console log. But it seems that core doesn't provide the information, because the build object which I can access with the script simple doesn't contain it. In the log you see: <=== [JENKINS REMOTING CAPACITY] ===>channel started The error mail ends with: <=== [JENKINS REMOTING CAPACITY] ===>

            Unassigned Unassigned
            bbio12 Carsten Kuhl
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: