Ah, good point! I needed to install the Authorize plugin in order to make the Job DSL plugin work:
> All Job DSL methods are whitelisted by default, but Jenkins access control checks are applied. These checks prevent users from gaining elevated permissions through Job DSL scripts. For this to work, the DSL job needs to run as a particular user. This is generally accomplished by installing and configuring the Authorize Project plugin. (https://github.com/jenkinsci/job-dsl-plugin/wiki/Script-Security) I guess I might just need to play around with the config a bit. Thanks, On Thursday, September 7, 2017 at 1:36:26 PM UTC-7, Daniel Beck wrote: > > > > On 7. Sep 2017, at 18:53, Daniel Lo Nigro <[email protected] <javascript:>> > wrote: > > > > I guess this is due to SECURITY-201 ( > https://jenkins.io/security/advisory/2017-07-10/) but now I'm not quite > sure how to accomplish what I want. How can I allow the projects to be > triggered as downstream builds of a remotely-triggered build, without > allowing anonymous users to trigger them directly? > > It looks like you have Authorize Plugin (or another plugin providing build > authorization) installed, but are not using it -- change that. > > -- 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/407ca8c2-4b40-4521-8196-857f2f1f1630%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
