Hi Peter, thanks for the reply;
On 29 January 2011 02:56, Peter Niederwieser <[email protected]> wrote: > > Why do you do a new checkout on every build? Are you trying to automate a > release procedure? > Yes, I would say we are; We do a nightly build of the trunk, which gives us the status of the release (if it were releaseable). Later, when we are ready, we can specify the tag which needs to be tested as 'the release'. What we have now (hacked together with Ant and InnoSetup etc) checks out from that tag, builds class files and jars through individual Ant builds, runs Junit tests and provides a report, runs cobertura and reports on code-coverage, and packages it all together with InnoSetup. > Have you considered using a continuous integration server (TeamCity, > Hudson/Jenkins, etc.) for this? > > No, not yet. Thanks for pointing it out. I notice it supports Gradle. I'll take a look at it. > Sean Van Buggenum wrote: >> >> Do I need to build this up myself, in the way I would anyway using Ant, >> (checkout myself, creating folders, programmatically selecting branch etc) >> > > Gradle doesn't yet ship with plugins for interacting with version control > systems. But that's usually just a tiny part (if at all) of what a build > does. So there's still a big difference between using Gradle and Ant. Also > it is much easier to implement custom tasks and workflows with Gradle/Groovy > than with Ant/Java/XML. For example, here is a small abstraction that allows > Gradle's own build to interact with Git: > https://github.com/gradle/gradle/blob/master/buildSrc/src/main/groovy/org/gradle/build/Git.groovy > > -- > Peter Niederwieser > Developer, Gradle > http://www.gradle.org > Trainer & Consultant, Gradle Inc. > http://www.gradle.biz > Founder, Spock Framework > http://spockframework.org > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/subversion-and-gradle-multiple-project-build-tp3360812p3361661.html > Sent from the gradle-user mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
