Just to serve as a reference for the rest of the Jenkins community that may stumble upon the issue outlined above, I have found a solution to the issue.
Per the Cloudbees documentation How to configure Access Control for Builds <https://support.cloudbees.com/hc/en-us/articles/209641937-How-to-configure-Access-Control-for-Builds> , the issue appears to be with the build authorization (made available via the Authorize Project Plugin <https://wiki.jenkins.io/display/JENKINS/Authorize+Project+plugin> ). The documentation states: ============================================================ The special case of the Reverse Triggering The reverse triggering is when the downstream job is configured to be triggered after the upstream job. When the build authorisations are configured triggers are executed by default as anonymous. If the upstream job visibility is limited, the downstream job won’t see the upstream and thus it won’t be triggered. To make such triggering working, you will have to configure the downstream job to run as a user having the permission to see the upstream job. ============================================================ In order to get the triggered job to trigger, I had to set the project Authorization to run as a specific user (my user Chuck Norris). After setting this value for the project Authorization, my downstream job was then triggered. Hopes this helps someone out there! -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Jenkins-downstream-jobs-not-triggered-after-enabling-security-tp4900460p4900500.html Sent from the Jenkins users mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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-users/1499952280317-4900500.post%40n4.nabble.com. For more options, visit https://groups.google.com/d/optout.
