Created by Caio Begotti on 2014-12-19 and last modified on 2015-01-09
Get this branch:
bzr branch lp:~ce-infrastructure/capomastro/deploy-mojo-jumpstart
Members of CE Infrastructure can upload to this branch. Log in for directions.

Branch merges

Related bugs

Related blueprints

Branch information

CE Infrastructure

Recent revisions

44. By Caio Begotti on 2015-01-05


43. By Caio Begotti on 2015-01-05

this doesnt matter much but okay...

42. By Caio Begotti on 2015-01-05

necessary to get the mojo spec processing the only external config template in the charm

41. By Caio Begotti on 2014-12-19

adds a test script to use mojo and capomastro mojo spec... ideally this repository will be emptied in the future as things are migrated and moved to the mojo spec but meanwhile this script can sit here so other people can give mojo a try to deploy capomastro

40. By Caio Begotti on 2014-11-27

Simplified Jenkins API relation so the upstream maintainers of its charm can possibly merge our custom charm without fuss.

39. By Caio Begotti on 2014-11-21

now that https://code.launchpad.net/~ce-infrastructure/capomastro/capomastro-jenkins-exposure-1155/+merge/242412 has been merged and SSO support has been landed as well, this is not necessary anymore, as discussed in the MR

38. By Caio Begotti on 2014-11-19

quick and dirty direct change to reflect the new launchpad group just created for access management

37. By Caio Begotti on 2014-11-18

This should go along with the changes of https://code.launchpad.net/~ce-infrastructure/capomastro/charm-sso/+merge/242104 as it is here that we set the OpenID options we'll use. As of now we're allowing users from the CE team as well anyone inside capomastro-users, which don't exist yet but we can be used as a placeholder for when we decide about how to organize the users of the service.

36. By Caio Begotti on 2014-11-14

So this is just a general cleanup to get the old branch that was sitting under lp:bygmester/capomastro-deploy in shape with the rewritten charms. Please take a look at the comments posted on https://bugs.launchpad.net/capomastro/+bug/1385221 because this deploy branch works ok but it is not necessarily useful for IS and production deployment IMHO.

35. By David Murphy on 2014-04-24

Cleaned up post-deploy-config to use branch instead of local tarball.

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.