I still feel like there could be better documentation around the Juju workflow actions, 'build-on-commit', 'build-bundle' etc. Specifically a numbered list (or similar) for the actions that will be performed.
For example:
Check git repository for changes, if changes continue
For each controller:
a. Deploy charm and run tests
b. Deploy reference bundle, run bundle tests
c. Deploy individual charms from bundle (not target charm), run charm tests
I feel there's not enough explanation as to what is happening or the purpose of the workflow.
I've looked at the documentation for cwr here:
https://jujucharms.com/u/juju-solutions/cwr-ci/ https://jujucharms.com/u/juju-solutions/cwr/
which is great :) .
I still feel like there could be better documentation around the Juju workflow actions, 'build-on-commit', 'build-bundle' etc. Specifically a numbered list (or similar) for the actions that will be performed.
For example:
For each controller:
a. Deploy charm and run tests b. Deploy reference bundle, run bundle tests c. Deploy individual charms from bundle (not target charm), run charm tests
I feel there's not enough explanation as to what is happening or the purpose of the workflow.