Add --show-report option to charm-build #135

Merged
merged 1 commit into from Mar 15, 2016

Conversation

Projects
None yet
4 participants
Member

johnsca commented Mar 15, 2016

This option enables a post-build report detailing what files have changed, based on the signatures in the existing .build.manifest

Contributor

chuckbutler commented Mar 15, 2016

YES!

Member

johnsca commented Mar 15, 2016

Making some refactors to use existing delta_signatures logic as suggested in IRC.

charmtools/build/__init__.py
@@ -588,6 +623,8 @@ def main(args=None):
default="http://interfaces.juju.solutions")
parser.add_argument('-n', '--name',
help="Build a charm of 'name' from 'charm'")
+ parser.add_argument('-r', '--show-report', action="store_true",
@marcoceppi

marcoceppi Mar 15, 2016

Owner

NIT: --report or --with-report?

charmtools/build/__init__.py
+ old_sigs = self.old_manifest['signatures']
+ if not old_sigs:
+ log.info('')
+ log.info('---------------------------------------')
@marcoceppi

marcoceppi Mar 15, 2016

Owner

Would we ever want report data to be machine readable?

Add --show-report option to charm-build
This option enables a post-build report detailing what files have
changed, based on the signatures in the existing .build.manifest
Member

johnsca commented Mar 15, 2016

Made some changes based on review.

@marcoceppi The report format is basically machine-readable but is still mixed in with the log output. I suppose we might want to dump it to a file at some point with less header info, but at that point it could maybe just be added to the .build.manifest file in a "changes" section or something.

Owner

marcoceppi commented Mar 15, 2016

LGTM :BOAT:

Contributor

bcsaller commented Mar 15, 2016

LGTM, thanks

marcoceppi added a commit that referenced this pull request Mar 15, 2016

Merge pull request #135 from johnsca/build-report
Add --show-report option to charm-build

@marcoceppi marcoceppi merged commit 9860721 into juju:master Mar 15, 2016

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment