On Mon, Aug 8, 2016 at 4:31 AM, Sverre Moe <[email protected]> wrote: > I just need the last build from an upstream dependency. The upstream build > cause might be an upstream dependency, or it may be an SCM cause. Such that > the upstream project might not be the upstream cause. Also an upstream cause > might be a downstream dependency.
Did not really follow that, but… > Later, when one of those downstream dependencies are built from SCM changes. > Lets say when they fixed the issues that previously failed their build > against the upstream project. Now they need to trigger a build of the all > upstream projects (if they previously failed because of this project). After > building a project I needed to get the previous build from an upstream > project to determine if it failed because of this one. Seems like it would be easier to roll this into one project with multiple `checkout`s, which could use `currentBuild.changesets` to decide whether or not to rebuild certain components. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1DpNDQHqgLZnbLLMOWd%3DrnXk4h_-yc%3DmD_7_%2BH7uu2og%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
