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
Originally reported by jinteck, imported from: Upstream and downstream multi-configuration projects triggering behavior
- assignee:
kohsuke
- status: Closed
- priority: Major
- component(s): remoting
- resolution: Fixed
- resolved: 2008-03-06T21:36:15+00:00
- votes: 0
- watchers: 0
- imported: 2025-11-25
Raw content of original issue
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
- environment:
Platform: All, OS: All
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
Originally reported by jinteck, imported from: Upstream and downstream multi-configuration projects triggering behavior
Raw content of original issue
Platform: All, OS: All