Job DSL

[Slide]

I've started looking into using the Job DSL plugin, as it looks like it will be awesome. I had a couple of questions that I hope someone might be able to answer.

I am planning on giving my users the control over their builds by allowing them to create a .build file which will be the definition of their build information. I would like to have some predefined build steps that are wrapped around the build steps they may add so that some setup can occur and then some post processing as well. I'd like this to be transparent to the users so that they could do something like this

build {

    name 'Some Name'

    steps {

        // some user defined steps here

     }

    recipients('list of email recipients')

}

When the job is generated, I'd like to insert a build step before and after their build step. 

The recipients is just a set of recipients that I will setup in email-ext, I can handle that part I believe.

Is it easiest to create my own Context subclass like JobContext? I haven't looked at the internals of the plugin much, would I be able to use "build" instead of "job" at the top level if I define a BuildContext?

Thanks!

slide 

[slide]

I was actually able to figure out all of this via monkey patching. It works great!