Closed MisterMartin closed 1 year ago
It looks like you don't have to use the hash anymore at all. Just using the tag name in the URL will behave like a branch name. Maybe this was always the case?
So, chords_control
needs to be modified to remove the silly 'Release-' construct (and associated hash machinations), and just offer branches, tags or release names. This will simplify things considerably.
Fixed in 674199d75f.
chords_control
uses the git tag hashes to download thedocker-compose.yml
file. This has worked all of the way up through Release 1.1.0-rc1. Suddenly it has stopped working, as documented below.If a branch name is used in the URL, instead of the tag hash, it still works. So I've created branches that match the recent releases.
For the time being, when configuring chords (with
chords_control
), use the branch name rather than the Release- name. (In spite of the warning fromchords_control
.)The following demonstrates the problem: