Not to drag the thread off-topic, but could you elaborate on any security issues with Job DSL? I experimented with it a while back, and CloudBees is going to demo Job Templates to my shop in the near future, but is there something that makes Job DSL inherently less secure-able than the latter?
For example, couldn't you just use project-based security to lock down the Job DSL job that creates and updates the spawned jobs? Thanks, On Friday, October 2, 2015 at 12:57:59 PM UTC-7, Baptiste Mathus wrote: > > +1 for the Job DSL plugin if you don't have hard security requirements on > your Jenkins instance. (i.e. all users are allowed to modify anything). > > 2015-10-02 20:37 GMT+02:00 Cuong Tran <[email protected] <javascript:>>: > >> Martin, >> >> We use the Templates plugin to simplify the job creation interface and >> standardize common job types. Combined with the folder plugin, we can >> restrict what can be created within a folder, making it even simpler for >> end users. The xml transformation isn't bad since you can just create a job >> with substitution tokens (${FOO}) and load it in from the interface. >> Changes to a template are automatically propagated to its jobs as well. >> You can also easily convert an existing job to use templates job. >> >> I think it's better than the other options you listed. >> >> Having said that, we have thousands of jobs and multiple Jenkins masters >> so this plugin doesn't work that well for our scenario. I think the >> general direction of keeping the job configuration in SCM (using >> combination of the workflow and Job DSL plugin) is more scalable and it's >> something we are investigating. >> >> On Thursday, October 1, 2015 at 12:53:36 PM UTC-7, Martin B. wrote: >>> >>> Hello users. >>> >>> I'm looking for independent opinions on the Jenkins Enterprise Templates >>> Plugin. >>> >>> It would be one of the main reasons for us to adopt Jenkins Enterprise, >>> but I was quite shocked to learn (see >>> >>> http://documentation.cloudbees.com/docs/cje-user-guide/temolate-sect-job-template-tutorial.html) >>> >>> >>> that you actually have to do raw XML transformation to get a simple job >>> template running. Looks rather bare bones to me. ('course I *can* see >>> where this might be useful with very complicated job templates, but I >>> like to keep the simple stuff simple, and telling people to write jelly >>> transformations isn't my idea of simple) >>> >>> Anyway - are you using JE Templates Plugin? Great Stuff? Much better >>> than (https://github.com/JoelJ/ez-templates) or >>> (https://wiki.jenkins-ci.org/display/JENKINS/Template+Project+Plugin) >>> ... ? >>> >>> cheers, >>> Martin >>> >> -- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/6a363e9f-ed64-4be8-a4a9-7dc68591c6d6%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/6a363e9f-ed64-4be8-a4a9-7dc68591c6d6%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Baptiste <Batmat> MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! > -- 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/603addc4-2433-412f-85a3-cd31eb19a41b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
