Upstream and downstream multi-configuration projects triggering behavior

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      JT Chu wrote:
      > Hi,
      > I have 2 multi-configuration projects. In my upstream project, there
      > are 2 slaves builds. Whenever, one of this slave build failed, the
      > upstream project was still triggering the downstream project. Is this
      > an expected behavior? The check box to trigger unstable build is set to
      > false in the post-build actions.

      There are bug in the downstream triggering from the matrix project —
      whereas it should trigger it once after all the configurations are
      built, currently each completed child build triggers the downstream.

      I remember someone just reported this bug in this list, and I thought I
      asked him/her to file a bug, but I still don't see it in the issue
      tracker, so please can you file one for us?


      Kohsuke Kawaguchi
      Sun Microsystems kohsuke.kawaguchi@sun.com

            Assignee:
            Kohsuke Kawaguchi
            Reporter:
            jinteck
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: