-
Bug
-
Resolution: Fixed
-
Major
-
Jenkins 1.563 RHEL6
Created three jobs: job A, job B, job C. Set job B config to be triggered after job A and to trigger job C. In this case, radio button in the section "build after other projects are built" cannot be saved (even if you save and reopen the configuration page). When job A is built, a NullPointerException is thrown and job B is not started (see attachments). If you chain only job B to job A, it works.
- is duplicated by
-
JENKINS-23083 Adding a second project to the list to trigger causes NPE
-
- Resolved
-
-
JENKINS-25758 NPE when triggering downstream job (again)
-
- Resolved
-
- is related to
-
JENKINS-16956 Require authentication for build triggers
-
- Resolved
-
-
JENKINS-22821 NPE when triggering downstream job
-
- Resolved
-
-
JENKINS-23083 Adding a second project to the list to trigger causes NPE
-
- Resolved
-
It seems there is still a problem, don't know whether it is the same: Previously the "build after other project"-trigger was a mirror of the post-build-action "Build other project". Now, you can alter the "Build other project" (e.g. removing job C from PBA of job B) and the trigger in job C is not updated. On the other hand changes in trigger of job C are not reflected in job B anymore. Actually the settings in job C have no effect, ie. when no PBA is configured in B, job C is never triggered, whatever it's configuration is.