lp:~ce-infrastructure/capomastro/deploy-jenkins-merge-1387601

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:~ubuntuone-hackers/capomastro/deploy

Daniel Manrique (community): Approve on 2014-11-26

Diff: 92 lines (+35/-10)

4 files modified

config/jenkins.yaml (+1/-1)
config/jenkins/hooks/install.d/bygmester (+20/-0)
deploy.sh (+6/-6)
init.sh (+8/-3)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #1387601: Merge back "upstream" the Jenkins API relation in its charm

Medium

Fix Released

Link a bug report

Related blueprints

45. By Caio Begotti on 2014-11-25

typo coming from the old branch url, my bad

44. By Caio Begotti on 2014-11-25

actually the simplest/smallest charm changes to get the API relation working are in a new branch now, pending review by the charmers team though

43. By Caio Begotti on 2014-11-25

until IS can review these timings lets simply give the charms more time to run, specially because on lcy01 it takes ages to deploy anything and i dont want to have problems with IO locally either

42. By Caio Begotti on 2014-11-24

my bad, apparently the extension relation we need is not available upstream but only from IS...

41. By Caio Begotti on 2014-11-24

since we still do not have it in the distro, we need to be explicit about the release from their own repository

40. By Caio Begotti on 2014-11-24

this should be enough to remove the branched jenkins charm we maintain for no reason today... the only downside is not having the private PPA setting available from the config.yaml directly, which is a shame but i cannot think of a better solution at the moment and nobody on #juju answered by doubt about this so...

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.