Readme Updates for Developer Workflow Usability

[arosales]

Suggest to add the following to improve the usability of cwr-ci in the developer workflow:

• charm-subdir action parameter: If a user has their charm embedded into a larger repository inform the user how to specify where the charm lives. Ensure cwr-ci only is invoked on charm change in sub-dir "mode."
• mention that cwr is a poll, every 5 minutes.
• Be explicit about where artifacts are put /srv/artifacts
• Be explicit on how to view CWR report
• Mention best practice for a reference bundle. For example, put a "test bundle" in a recommended bundle that can be specifically for testing by all. Also be more specific that folks and upload their own customer reference bundle -- good in the context of OpenStack which will always have a reference bundle.
• Put a note on how to track running jobs. Should folks ssh into Jenkins?
• Recommendations on how to use resources

For tool componentry add links to:

• Add links to https://github.com/juju-solutions/bundletester
• Add links to https://github.com/juju-solutions/matrix
• Add links to https://github.com/juju-solutions/cloud-weather-report
• Add links to https://github.com/juju/python-libjuju

[kwmonroe]

I've addressed most of these points in https://github.com/juju-solutions/bundle-cwr-ci/commit/8e1b1050e58eccf137972e2aa5a2dae3a42b032a. Would you mind giving it another read at:

https://github.com/juju-solutions/bundle-cwr-ci/blob/master/README.md

Two things i wasn't clear on:

• Mention best practice for a reference bundle. For example, put a "test bundle" in a recommended bundle that can be specifically for testing by all. Also be more specific that folks and upload their own customer reference bundle -- good in the context of OpenStack which will always have a reference bundle.

Do you mean put a separate bundle.yaml in a recommended bundle to be used by CWR?

• Recommendations on how to use resources

I don't think the cwr charm supports pushing/releasing charms with resources at all at this time. Definitely worthy of a separate issue if this is what you meant.