THORNode smoke tests don't display Midgard commit hashes
A THORNode smoke test tries to pull a Midgard branch of the same branch name and uses it for its Midgard comparison, convenient for making THORNode and Midgard changes simultaneously.
When such a branch doesn't exist, the smoke test uses the Midgard develop
branch and shows a message on the lines of
Cloning into 'midgard'...
warning: Could not find remote branch Multi/EventVersion to clone.
fatal: Remote branch Multi/EventVersion not found in upstream origin
Cloning into 'midgard'...
develop: Pulling from thorchain/midgard
(example).
When such a branch exists, the smoke test instead shows
Cloning into 'midgard'...
docker pull registry.gitlab.com/thorchain/midgard:develop || true
develop: Pulling from thorchain/midgard
.
Here are examples from the same commit, but for different Midgard branches
(the first failing with a Midgard error, the second succeeding):
https://gitlab.com/thorchain/thornode/-/jobs/3768058704
https://gitlab.com/thorchain/thornode/-/jobs/3768132316
I noticed that it was inconvenient or infeasible to keep track of or to intuitively show to others which Midgard commits were used for which smoke tests, since a branch of a given name can be changed many times before and after it is used for a smoke test (particularly during troubleshooting).
I currently propose that commands of the form
git ls-remote $MIDGARD_REPO $CI_COMMIT_REF_NAME
and
git ls-remote $MIDGARD_REPO develop
be used to display the Midgard commit used for a given smoke test,
which can then easily be looked at with
https://gitlab.com/Multipartite/midgard/-/commit/[hash]
and its previous commits with
https://gitlab.com/Multipartite/midgard/-/commits/[hash]
.