I found an active bug report that is relevant for my problem
https://issues.jenkins-ci.org/browse/JENKINS-29807
tirsdag 1. september 2015 09.06.33 UTC+2 skrev Sverre Moe følgende:
>
> I don't understand what the problem is, but it is happening again, and
> none of the projects are disabled this t
I don't understand what the problem is, but it is happening again, and none
of the projects are disabled this time.
fredag 28. august 2015 15.25.23 UTC+2 skrev Sverre Moe følgende:
>
> I had 3 downstream projects which was disabled. Two of them caused no
> trouble, because it just skipped them
>
I had 3 downstream projects which was disabled. Two of them caused no
trouble, because it just skipped them
project3 is disabled. Triggering skipped
When I removed the upstream project from each disabled downstream projects
reverse build trigger, then everything worked fine.
fredag 28. august
I have taken a look into the code of ReverseBuildTrigger where the
NullPointerException happens:
111 boolean downstreamVisible = jenkins.getItemByFullName(job.getFullName())
== job;
But still no closer to the solution...
It looks like the problem lies with authentication.
fredag 28. august 201
Using Jenkins 1.626
I have configured 19 projects with a reverse build trigger "Build after other
projects are built".
After building the upstream project, these 19 projects (minus those disabled)
should be triggered as well.
I have rechecked the configuration for every downstream projects.
