Templates Plugin (Jenkins Enterprise)

[Martin Ba.]

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

[Cuong Tran]

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.

[Baptiste Mathus]

+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).

--
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 jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6a363e9f-ed64-4be8-a4a9-7dc68591c6d6%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

[0xCDC...@gmx.at]

Thanks!

 

I'm looking at dozens of similar jobs at the moment and only a single master, so I guess I'm in a smaller boat that you atm.

 

What scares me with regard to the Xml transform is that I'm not sure subtle errors slipping through especially when changing an existing template

for existing jobs. Well I guess there's nothing for it but to try it in depth for myself.

 

Could you comment further on the second option you mentioned? (workflow + job DSL)

Keeping Job defs in SCM certainly seems intriguing.

 

chhers,

Martin

 

Gesendet: Freitag, 02. Oktober 2015 um 20:37 Uhr
Von: "Cuong Tran" <cuong...@gmail.com>
An: "Jenkins Users" <jenkins...@googlegroups.com>
Betreff: Re: Templates Plugin (Jenkins Enterprise)

[Walter Kacynski]

I use the Enterprise Templates extensively.  They are very powerful but difficult to debug at times.  I run a second "Test" master that I use to stage template changes to make sure that everything goes as planned before issuing updates to my production jobs.  The great thing about these is that you can dynamically change the logic of a build job by inventing your own job attributes.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.

[Martin Ba.]

>> ... you can dynamically change the logic of a build job by inventing your own job attributes. <<

Could you elaborate? I don't quite follow.

cheers,
Martin

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/18996fc2-0e92-4bb4-98a1-3084d1c97568%40googlegroups.com.

[Brian Ray]

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,

[Daniel Beck]

On 06.10.2015, at 18:52, Brian Ray <be_...@sbcglobal.net> wrote:

> 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?

The problem is that a user with Job/Configure on a single freestyle job can add a Job DSL build step there, and wreaks havoc on your instance.

[Victor Martinez]

Hi,

 Let me kindly suggest the below security approaches in case  you need to secure your Jenkins instance:

• https://wiki.jenkins-ci.org/display/JENKINS/Ownership-Based+security
  
• https://wiki.jenkins-ci.org/display/JENKINS/Job+Restrictions+Plugin

There are some use cases it will not be enough but it depends on how much security you need in place.

I hope it helps

Cheers

[Brian Ray]

Aha. Got it.