Report hash of branch revisions

[Thomi Richards]

This is a feature request. If the codetree maintainers agree to the feature, I'm happy to write the code and submit a MP.

As part of our service deployment strategy, we're deploying new services with every new code revision, rather than upgrading charms / service code. Currently our mojo spec includes code that reads the 'collect' file and produces a unique hash based on the branch names and revisions. That hash is then incorporated into the juju service name.

To do this, we have ended up re-writing much of the codetree config file parsing routines. I'd like to include that functionality inside codetree itself. My idea is to add a new option to codetree: '--print-hash'. If set, instead of codetree actually building the branches on disk, it would print something like:

~~~
branch_hash: 8b1a9953c4611296a827abf8c47804d7
~~~

This hash is built from the branch locations and their current revisions (or their pinned revisions, in the case of 'revno=X' in the config file).

What do the codetree maintainers think? Is this something you'd consider adding to codetree itself?

[Tom Haddon (mthaddon)]

Sure, this sounds like a good idea. Happy to review when if/when you have a branch.

[Tom Haddon (mthaddon)]

Note that there is now a related bug about this in Mojo: https://bugs.launchpad.net/mojo/+bug/1541405. Would this address the issue for you?

[Jacek Nykis (jacekn)]

Most likely https://bugs.launchpad.net/mojo/+bug/1541405 makes this change unnecessary.

I will set this bug to incomplete and let it expire unless requester says it's still relevant.