to me jenkins jobs should be version controlled too. you should be able to check out jenkins configurations from VCS and create/execute jobs via gradle. I don't know much about jenkins, but should be doable.
Over time, the type of jenkins jobs you run can change drastically. This knowledge will be lost from version to version unless you check the jenkins config into VCS. I think we are saying the same thing largely here... does this make sense? On Fri, Sep 30, 2011 at 10:23 PM, Hans Dockter <[email protected]>wrote: > 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 <[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? >> > >
