It is related somewhat. That issue is about getting the upstream build that triggered this running build. 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.
When a project is building, it triggers a build of all its downstream dependencies to verify they work with the new changes. If any of the downstream dependencies fail, then also the upstream project should fail. I add a BadgeAction with the list of failed downstream projects to the build for later inspection. 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. fredag 5. august 2016 22.00.34 UTC+2 skrev Jesse Glick følgende: > > On Fri, Aug 5, 2016 at 4:02 AM, Sverre Moe <[email protected] > <javascript:>> wrote: > > Variable currentBuild irefers to the currently running build. What I > needed > > was the last build of a upstream dependency. > > Like JENKINS-31576 you mean? > -- 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/34cabeb4-bdf4-4ccc-909a-1d4bf51917a0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
