4
4
Publish charm tests organized around:
8
9
- other tags? (i.e., "main")
9
11
for each charm in the official charm store.
11
For each configured test environment (specifying {provider, series}),
12
For each charm in the official charm store,
13
the charm tester will:
14
- run charm-graph-tests
15
- run charm unit-tests
13
For each configured test environment (specifying {provider, series}) and each charm in the official charm store, the charm tester will:
15
- run charm-graph-tests
16
- run charm unit-tests
23
- jenkins.qa.ubuntu.com
24
- jenkins.qa.ubuntu.com
24
25
- `API_TOKEN` to programmatically drive charmtesting
26
27
- charmtester (separate from and subordinate to jenkins... eventually)
27
28
- creates(/removes?) jobs based on the current charm list
28
29
one job per charm... `$series-$provider-charm-$charm_name`
30
- runs charm-graph-tests
31
- runs charm unit-tests
31
- runs charm-graph-tests
32
- runs charm unit-tests
32
33
- configured with environment(s) for this slave to test against
36
37
- updates test components regularly(?)... juju, charms, plans
37
- currently only on upgrade: (needs to be lighter-weight)
39
- wipe/rebuild the master charmset regularly (this is used only to generate dependency graphs)
40
- wipe/rebuild the lxc cache regularly for local provider
41
- destroy and rebootstrap regularly to remove stale state (?)
38
- currently only on upgrade: (needs to be lighter-weight)
40
- wipe/rebuild the master charmset regularly (this is used only to generate dependency graphs)
41
- wipe/rebuild the lxc cache regularly for local provider
42
- destroy and rebootstrap regularly to remove stale state (?)
43
44
- charm test runner (curl with an `API_TOKEN` wrapped in a cronjob)
48
- pulls a master charmset
49
- generate test plans based on dep graphs (graph-test is the set of test plans for that charm)
51
- pulls the charms for each run (separate from graph generation)
53
- spins up each plan in the graph-test, watching for success/fail of each plan
49
- pulls a master charmset
50
- generate test plans based on dep graphs (graph-test is the set of test plans for that charm)
52
- pulls the charms for each run (separate from graph generation)
54
- spins up each plan in the graph-test, watching for success/fail of each plan
56
- just hit `$CHARM_DIR/tests/test` and run screaming?
57
- maybe sandbox this a little
57
- just hit `$CHARM_DIR/tests/test` and run screaming?
58
- maybe sandbox this a little
62
63
- update charmrunner to work against other providers (currently local-only)
64
65
- persist job stuff between instances (address backups _and_ availability)
67
68
- charmtester needs to:
68
- use lighter-weight updates for test components
69
- trigger by commit-hooks
70
- only re-run charms that have diffs
71
- handle deletions from the charm list
69
- use lighter-weight updates for test components
70
- trigger by commit-hooks
71
- only re-run charms that have diffs
72
- handle deletions from the charm list
73
74
- turn charmrunner into juju-jitsu plugins