Capomastro

Merge back "upstream" the Jenkins API relation in its charm

Bug #1387601 reported by Caio Begotti on 2014-10-30

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Capomastro	Fix Released	Medium	Caio Begotti

Bug Description

We need to merge back upstream (if possible) the Jenkins API relation we're using to talk to it from Capomastro as the current charm in the store does not support it even if the Jenkins service actually does.

Related branches

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

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

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

lp:~caio1982/charms/trusty/jenkins/trunk

Merged into lp:charms/trusty/jenkins at revision 33

Marco Ceppi (community): Approve on 2015-01-07

Review Queue (community): Needs Fixing (automated testing) on 2015-01-06

lp:~ce-infrastructure/capomastro/deploy-mojo-jumpstart

Merged into lp:~ubuntuone-hackers/capomastro/deploy at revision 41

Daniel Manrique (community): Approve on 2015-01-05

Caio Begotti (caio1982) on 2014-10-30

Changed in capomastro:
assignee:	nobody → Caio Begotti (caio1982)

Revision history for this message

Caio Begotti (caio1982) wrote on 2014-11-24:

Hmm apparently now there's an extension hook available, so it seems merging our changes will be easy.

Changed in capomastro:
status:	New → Confirmed

Revision history for this message

Caio Begotti (caio1982) wrote on 2014-11-25:

My mistake, the current extension hook from the IS charm enters an infinite setup loop with our charm when we set relations between the services because it's meant to be used by subordinate charms, which is not our case here even though the relation code is nearly 90% of what we need. We'll need to merge the API relation we had upstream after all...

Revision history for this message

Caio Begotti (caio1982) wrote on 2014-11-25:

MR created at https://code.launchpad.net/~caio1982/charms/trusty/jenkins/trunk/+merge/242801