update charms in place whitelist
This needs to be reconciled against
http://bazaar.launchpad.net/~clint-fewbar/juju/charm-tests-spec/view/head:/source/charm-tests.rst
Publish charm tests organized around:
for each charm in the official charm store.
For each configured test environment (specifying {provider, series}) and each charm in the official charm store, the charm tester will:
Jenkins
API_TOKEN
to programmatically drive charmtestingcharmtester (separate from and subordinate to jenkins... eventually)
$series-$provider-charm-$charm_name
charm test runner (curl with an API_TOKEN
wrapped in a cronjob)
charm-install-test
started
charm-graph-test
charm-unit-test
$CHARM_DIR/tests/test
and run screaming?update charmrunner to work against other providers (currently local-only)
persist job stuff between instances (address backups and availability)
charmtester needs to:
turn charmrunner into juju-jitsu plugins
jenkins openid plugin (?)
jenkins slaves working
maybe use splice to simplify the charmtester charm itself... need storage, charm testing, jenkins, etc
use lp tools... is there a way to just watch the ppa?
building
Use the following URL to trigger build remotely: $JENKINS_URL/job/$job_name/build?token=TOKEN or /buildWithParameters?token=TOKEN Optionally append &cause=Cause+Text to provide text that will be included in the recorded build cause. http://charmtests.markmims.com/job/jenkins/build?token=TOKEN
notifications / publication
$JENKINS_URL/job/$job_name/api/json
grab the field "color" it's either "red" or "blue"