>
> On Mon, Aug 8, 2016 at 4:31 AM, Sverre Moe <[email protected]
> <javascript:>> 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…
>
The project that is currently building might have previously been triggered
by an upstream project, a component it has as a build dependency with.
So the Upstream Cause which triggered a new build might either be an SCM
change or another jenkins project.
A
/ \
B C
/ \ \
D E F
* SCM change triggers a build of A.
* The Verification stage triggers a build of B, C, D, E
* The build of B fails and consequently so does A.
...
* SCM change triggers a build of B.
* The Verification stage triggers a build of D and E.
* The build succeeds and so does all its downstream dependencies.
* Now it needs to rebuild A. It checks if the previous build of A failed
because of this project.
So the upstream build cause might either be an upstream dependency or a
downstream dependency.
> 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.
>
Not sure what you ment with that. We have aprox 70 git repositories of
libraries, utilities, programs with various dependencies among them. Some
have many dependencies, some have few and some have none.
When someone push changes to remote, the git server has a hook that calls
Jenkins URL with notifyCommit to trigger a build of that project.
--
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/fa96b5b4-8d61-4d13-bd83-95a228715c03%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
