Yes. We think that would be a great feature. I had recently a chat about this with Stefan Wolf, a Jenkins committer.
Here is why we think that would be a cool feature: - CI Jobs are version controlled (specified in the build script). So for example you can set them easily up for older versions. - You may have many jobs per project. They may vary over time. You might have for example multiple jobs just for executing a set of integration tests to use the distribution feature of Jenkins. You might have one just for compiling (in some large projects), one for unit tests, .... You also might have multiple branches living on Jenkins. So being able to automize the Jenkins set up may save a lot of time to some projects. Think also about short lived feature branches with Git. Hans -- Hans Dockter Founder, Gradle http://www.gradle.org, http://twitter.com/gradleware CEO, Gradleware - Gradle Training, Support, Consulting http://www.gradleware.com On Fri, Sep 30, 2011 at 9:15 PM, phil swenson <phil.swen...@gmail.com>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? >
