Juju as a software release platform

[Bruce Edge]

I know that Juju is targeted at the service provisioning layer, but
I'm wondering about possible integration with the in-house
dev/build/qa/promote/release cycle.
Where does that come into the equation, or is it even part of it? This
is the next layer that needs to be addressed once the automated
provisioning is in place.
What it everyone doing for this part of the problem?

For example take a jenkins config that's spitting out regular builds.
Some are promoted to QA, and others to staging and/or production. Is
there any preferred mechanism for integrating this build promotion
process into juju based deployments?
I suppose one way to manage this would be to build the apps into
debian packages and the versioning in sources.list.d/in-house.list
files. However this would still require a manual upgrade cycle to pull
down the latest packages and you'd need a tool to manage the package
repo selections that correlated somehow with available CI generated
builds.

I'm not looking for the depth of features provided by the udeploy or
electric-deploy comercial apps, but some skeleton feature set of that
functionality to manage in-house releases on juju provisioned
environments.

One more requirement is that I'm looking to re-use existing CI
generated binaries and not push out source to be built in-place.


-Bruce