Best practice to continuously integrate application updates

Denis Weerasiri ddweerasiri at
Wed Jul 2 03:16:22 UTC 2014

Thanks Andrew.

On Wed, Jul 2, 2014 at 1:02 PM, Andrew Wilkins <andrew.wilkins at
> wrote:

> On Wed, Jul 2, 2014 at 10:47 AM, Denis Weerasiri <ddweerasiri at>
> wrote:
>> Hi,
>> I mentioned the command as "charm-update". But it should have been
>> "upgrade-charm"
>> On Wed, Jul 2, 2014 at 12:44 PM, Denis Weerasiri <ddweerasiri at>
>> wrote:
>>> Hi,
>>> Support I have written a charm to deploy a web application on top of
>>> tomcat. And now I need to redeploy the web application when I update the
>>> source repository of the web application. What is the best practice to do
>>> this?
>>> What I have in mind is to write a new version of charm and use
>>> charm-update command. So juju will re-deploy the web application.
> A charmer will be able to give you better directions, but what existing
> charms do is have a source revision (and maybe repository) charm config
> setting.
> You would then do "juju set myapp revision=<rev>", which would trigger a
> config-changed hook call in your charm. The charm is then responsible for
> pulling down the new revision and restarting the application.
> HTH,
> Andrew

Denis Weerasiri

Sent from my iPhone
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Juju mailing list