Juju-core daily build

[William Reade]

On Wed, 2013-02-06 at 20:13 +1100, David Cheney wrote:
> Hello,
> 
> I have setup a daily build of juju-core so I can catch integration 
> issues*. This build is primarily so I can catch new deps added to the 
> build process so I don't have to scramble to fix them on a Saturday morning.
> 
> https://code.launchpad.net/~dave-cheney/+recipe/juju-core-daily
> 
> Please let me know if it is useful for you

Thank you for doing this, I think it's effort well spent.

It crosses my mind that we really need to completely automate the
process of propagating a new release to all the places it needs to get
to [0]. How feasible would it be to do, on top of this work, a daily
build-and-distribute to all those places?

I think you've got the best perspective on this: how much work would we
have to do to get to the point where pushing a new release of juju was a
one-step operation, that we could do and did every day? And, if that's
impractical, how close can we reasonably get?

> Dave
> 
> * I haven't seen it pass, yet, but it will eventually
> 

Two out of three ain't bad ;).

Cheers
William

[0] not just archives, but a bunch of ec2 buckets, probably some HP
ones, probably more providers, probably some global openstack bucket so
that people on private clouds can still update juju, etc etc