Continuous deployment for Grails Plugins?

[Aaron Zirbes]

We have a rather convenient CI/CD setup here at the U of MN for our Grails applications, but I'd like to get something working just as smoothly for all of our internal plug-ins.

Our plugins are currently pulled from a couple different internal "GrailsRepo" SVN repositories, and it seems that this isn't where we want to be?

Based on http://blog.springsource.org/2010/05/18/managing-plugins-with-grails-1-3/ it looks like the way to go is to:

 * Set up an Artifactory server or two to serve as a MavenRepo for our Grails projects

 * have the Jenkins CI servers automatically build and package the plugins, then publish the plugin zip file artifacts to the Artifactory server

Is this what others are doing?  Does this seem sane?  Any suggestions or pointers?  Thanks!

--

Aaron

[Rick Cochrane]

Aaron!

Long time, man.  Sounds like you guys have been busy.  As an aside, I nearly ended up using your mock auth for Spring Security plugin the other day - nice work!

The approach you referenced below sounds just like what we're doing - except we're still Hudson (soon to be Jenkins!), and Nexus rather than Artifactory.

Take care,
Rick

--
You received this message because you are subscribed to the "Groovy Users of Minnesota" group.
 
To post to this group, send email to groo...@googlegroups.com
To unsubscribe from this group, send email to groovymn-u...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/groovymn?hl=en

[Ted Naleid]

With git/mercurial, I've used submodules/subrepos with plugins "installed" as a local plugin.  I think you can do the same sort of thing with svn externals, but I'm guessing it wouldn't be as clean.

The nice thing about this method is that it avoids the whole compile, package, deploy to maven repo steps as well as all the snapshot versioning stuff.  Makes things much quicker. 

It might not scale that well though if you've got a _lot_ of internal plugins that you're using, but for a few that you're doing lots of iteration on, this can be a huge time saver.

Publish the stable plugins and use subrepos/internal plugins for the things you change often.

-Ted

[Aaron Zirbes]

Thanks for the responses!  As I'm looking for a full-automated solution, I'll stick with the (Git/SVN) -> Jenkins -> Artifactory -> mavenRepo -> my-grails-app route.

Thanks Rick for the confirmation that a similar (Hudson/Nexus) setup works for you.

I'll try to remember to write up what I found when I finish in case anyone is interested.

--

Aaron