Created by Laurent Sesques and last modified
Get this branch:
bzr branch lp:~sajoupa/mojo/fonts-mojo-spec-update-content
Only Laurent Sesques can upload to this branch. If you are Laurent Sesques please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Laurent Sesques
Mojo: Continuous Delivery for Juju

Recent revisions

18. By Laurent Sesques on 2016-01-04

[sajoupa] missing .sh in filename, import os and refactored mojo.project import

17. By Tom Haddon on 2016-01-04

[sajoupa,r=mthaddon] New manifest to update the site content, using an updated mojo_utils.py. Replaced sleep with juju-check-wait in mojo-how-to's manifest-update-content

16. By Tom Haddon on 2015-12-23

[sajoupa,r=mthaddon] added ksplice collect, better relations syntax, explicit path to add-floating-ip

15. By Laurent Sesques on 2015-12-21

[mthaddon,r=sajoupa] Mojo now supports a "juju-check-wait" phase, which confirms the environment has reached a steady state and that juju status is clean. Update fonts.u.c, mojo.c.c and juju-intro specs to use that. [sajoupa,trivial] corrected a typo (we're using nagios, not naigos)

14. By Gareth Woolridge on 2015-12-18

[sajoupa, r=moon127] Landing sajoupa's initial work on font.ubuntu.com spec

13. By Tim Kuhlman on 2015-11-18

[mthaddon,r=timkuhlman] Switch to only one IP on production so we can free up a floating IP for another serivce

12. By Tom Haddon on 2015-10-20

[mthaddon,trivial] Use new stop-on phase to avoid errors for when we have no diff between production and devel in autodeploy

11. By Paul Collins on 2015-10-14

[mthaddon] add autodeployment mechanisms for mojo-how-to

This only addresses updating built content, not charm upgrades, which will need further work.

10. By Tom Haddon on 2015-09-21

[mthaddon,trivial] add the verify scripts tot he mojo-how-to spec

9. By Paul Collins on 2015-09-17

[mthaddon] Add a "juju-intro" service which uses the charms described on https://jujucharms.com/docs/stable/getting-started so that we can test these actually work in CI

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
This branch contains Public information 
Everyone can see this information.