Why would you do this though? I've always scheduled jobs to run or have them run when a specific branch is pushed to the repo. See http://blog.james-carr.org/2011/09/09/my-current-java-workflow/ for my current setup. :)
I do however have a few gradle scripts that I execute from jenkins to do some common build process tasks, such as automatically bumping the next snapshot version up and pushing that change back to the development branch. There should be no problem however interacting with jenkins in gradle by using the REST API for jenkins and RestClient (http://groovy.codehaus.org/modules/http-builder/doc/rest.html). I definitely recommend RESTClient as I use it on several projects for various things. Thanks, James On Fri, Sep 30, 2011 at 3:15 PM, phil swenson <[email protected]> wrote: > has anyone tried controlling/launching jenkins jobs from gradle? > so instead of going to jenkins UI and clicking "build now", you might have a > gradle task: > gradle jenkinsSnapshot > comments? --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
