Charm needs to be a subordinate

[marcoceppi]

because it's sexier that way

[mmm]

This charm's got a few distinct bits:

• jenkins itself w/ some specific plugins we should update lp:charms/jenkins to handle "core" plugins, where the plugin versions have to match the jenkins version exactly
• bits that set up the instance to be a juju client we should update lp:charms/juju and use it for this purpose
• bits that create charm test jobs for jenkins this is the sub that charmtester will become... it really only creates jobs for the testing tool (jenkins or travis or ...)
• bits that run tests this has already been replaced with jitsu test for embedded charm tests need to replace graph tests with raw charmrunner

So, the whole shebang should work something like:

juju deploy --config precise-ec2-tester.yaml jenkins precise-ec2-tester
juju deploy --config ec2-testing-account.yaml juju
juju add-relation precise-ec2-tester juju
juju deploy charmtester
juju add-relation jenkins charmtester

[mmm]

once this happens, we can start using config-changed... yay! i.e., we need to move more logic to config-changed once we have this split up. Need to look through the upgrade story eventually too, but they're daily ephemeral builds atm, so it doesn't really matter. We'd like them to live longer and run charm tests per commit on each charm... eventually.