I would certainly like to, though I'm very time constrained and wouldn't want to push out a series of poorly written posts. But It's been a great learning experience so I'll see what I can do and drop you a line when I got something publishable.
On 19 Jan 2012, at 03:03, Luke Daley wrote: > On 18/01/2012, at 2:22 PM, Sebastian Gozin <sebastian.go...@gmail.com> wrote: > >> I use the jenkins build pipeline plugin in combination with grails and >> gradle scripts. >> There isn't much to it as you already pointed out that in maven the >> artifactId isn't parametrizable. In gradle you can just use environment >> variables to set the version as needed. >> >> What I actually do is I move a new commit through a series of branches >> (unit, integration, functional, staging, master) using the jenkins git >> plugin and tagging them as they move from one branch to the other. (I have >> chosen not to dirty my commit history with release commits) >> Finally at the end I take the fully tested commit and run a release+deploy >> build which just uses the build number as the version number as I found >> explicitly managed version management to be too costly if you deploy to >> production often and have little time. >> Each build step in the pipeline is just regular grails or gradle plugin >> usage so nothing special there. >> >> Which gives me: >> - a stable master branch >> - automated data migration testing >> - automated deployment to production given all previous tests work >> >> Which is incredibly easy to get used to. >> > > This sounds really cool. Have you considered sharing blog posts on your work? > >> Cheers, >> Sebastian >> >> >> On 18 Jan 2012, at 21:55, Mikael Andersson wrote: >> >>> Hi >>> >>> I'm trying to find out how to setup a continuous delivery pipeline and >>> struggling a bit to find information about existing setups using open >>> source tools. >>> >>> Currently our build is maven based which isn't great when using SNAPSHOTs >>> and wanting the ability to treat each artifact which passes all tests as >>> releasable. I'd like each successful build to result in a non-SNAPSHOT >>> artifact with build information like revision in the manifest. Quite >>> possible that there is a way to do this with maven but so far I haven't >>> found a way since the artifactId isn't parametrizable. >>> >>> Jenkins Build Pipeline plugin looks interesting haven't used it yet but it >>> would be great to use that in cooperation with gradle to achieve a build >>> pipeline where each build could potentially be released after unit tests, >>> integration test and possible manual sign-off has been performed. >>> >>> I'm really curious find information about how existing gradle and open >>> source tool based continuous delivery setups out in the wild work. >>> >>> Cheers, >>> Micke >> >> >> --------------------------------------------------------------------- >> 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 > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
