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

Release Build is marked as failure for multi-module projects.

    XMLWordPrintable

Details

    Description

      When I run a m2release on a multi-module, it shows up as a failure. Here is the last bit in the output of the console:

      [INFO] ------------------------------------------------------------------------
      [INFO] BUILD SUCCESSFUL
      [INFO] ------------------------------------------------------------------------
      [INFO] Total time: 1 minute 13 seconds
      [INFO] Finished at: Wed Oct 06 08:29:50 MDT 2010
      [INFO] Final Memory: 31M/409M
      [INFO] ------------------------------------------------------------------------
      channel stopped
      Email was triggered for: Failure
      Sending email for trigger: Failure
      Sending email to: [removed]
      Notifying upstream projects of job completion
      Finished: SUCCESS
      

      Attachments

        Issue Links

          Activity

            lynggaard lynggaard added a comment -

            Put in null guard in downstream view plugin.

            lynggaard lynggaard added a comment - Put in null guard in downstream view plugin.
            lynggaard lynggaard added a comment -

            Adding downstream-view to component list

            lynggaard lynggaard added a comment - Adding downstream-view to component list

            I removed downstream-view from my instance of hudson, since it was causing long startup times and was not really using its functionality.

            I now don't show a failed build, but on each module for the release build, it doesn't show their console output. Here is the console output:

            Started
            Build failed before it gets to this module
            Finished: NOT_BUILT
            

            I'm guessing this is probably impossible with the way the release plugin works... So this bug is really in the downstream-view.

            lshatzer Larry Shatzer, Jr. added a comment - I removed downstream-view from my instance of hudson, since it was causing long startup times and was not really using its functionality. I now don't show a failed build, but on each module for the release build, it doesn't show their console output. Here is the console output: Started Build failed before it gets to this module Finished: NOT_BUILT I'm guessing this is probably impossible with the way the release plugin works... So this bug is really in the downstream-view.
            teilo James Nord added a comment -

            Hudson doesn't know anything about the released modules when the release is performed as this is done in a new instance of maven that hudson is not intercepting.

            teilo James Nord added a comment - Hudson doesn't know anything about the released modules when the release is performed as this is done in a new instance of maven that hudson is not intercepting.

            Code changed in hudson
            User: : kohsuke
            Path:
            trunk/hudson/plugins/downstream-buildview/src/main/java/org/jvnet/hudson/plugins/DownstreamBuildViewUpdateListener.java
            http://jenkins-ci.org/commit/36450
            Log:
            [FIXED JENKINS-7691] applied a patch

            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in hudson User: : kohsuke Path: trunk/hudson/plugins/downstream-buildview/src/main/java/org/jvnet/hudson/plugins/DownstreamBuildViewUpdateListener.java http://jenkins-ci.org/commit/36450 Log: [FIXED JENKINS-7691] applied a patch

            People

              shinodkm shinodkm
              lshatzer Larry Shatzer, Jr.
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: