Guys,

I've been doing some thinking lately (yes, I know I shouldn't - I've heard
this from good friends before, but can't help it) and it makes more and more
sense to me to wrap more build/deploy functionality into our Gradle build.

The low-hanging fruits I have in mind right now is to provide a wrapper for
{{puppet apply bigtop-deploy/puppet/manifests/site.pp}} that will do a few
things like:
 - copy deployment recipes to all specified hosts, including site.csv file
 - start puppet apply on all hosts in parallel using gradle ssh plugin

This, IMO, will provide us with a very easy and transparent way of quickly
deploying cluster bits as one works on something, without switching out of the
convenient build environment. Sorta, change-deploy-rinse-and-repeat loop.

The same gradle task can be called, if desired from Jenkins or else.

Do you think it worth it? Thoughts?
-- 
Take care,
  Cos

Reply via email to