Q: what committish is in the client job dump in con/tinuous?

[yarikoptic]

sorry if I forgot but looking at

(git)smaug:…datalad/ci/git-annex-ci-client-jobs/builds/2022/03[master]push-result-s
$> grep . */result-smaug-*/git-annex.rc
handle-result.yaml-10-b8410b5a-success/result-smaug-614/git-annex.rc:0
handle-result.yaml-11-be9c5955-success/result-smaug-615/git-annex.rc:124
handle-result.yaml-5-8ff806f4-success/result-smaug-609/git-annex.rc:1
handle-result.yaml-6-28b0bfae-success/result-smaug-610/git-annex.rc:0
handle-result.yaml-7-d71c51e3-success/result-smaug-611/git-annex.rc:0
handle-result.yaml-8-7b1cb071-success/result-smaug-612/git-annex.rc:0
handle-result.yaml-9-5a6dea48-success/result-smaug-613/git-annex.rc:0

I failed to find where those b8410b5a etc belong to. I thought that they should correspond to upstream's git-annex commits, but I fail to describe them:

(git-annex)lena:~/proj/git-annex[master]git
$> git pff
Already up to date.

$> git show b8410b5a
fatal: ambiguous argument 'b8410b5a': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

[jwodder]

@yarikoptic Those are the commit hashes of the result-* branches of the datalad/git-annex-ci-client-jobs repo that the workflow ran on (and which the workflow deletes at the end of the run).

[yarikoptic]

cool, thanks. FTR -- we would need to grep explicitly for the version of git-annex

(git)smaug:…datalad/ci/git-annex-ci-client-jobs/builds/2022/03[master]push-result-s
$> git grep 'git-annex version'
handle-result.yaml-10-b8410b5a-success/result-smaug-614/git-annex.log:git-annex version: 10.20220222+git60-g54a43f68e-1~ndall+1
handle-result.yaml-11-be9c5955-success/result-smaug-615/git-annex.log:git-annex version: 10.20220222+git62-gce523f756-1~ndall+1
handle-result.yaml-5-8ff806f4-success/result-smaug-609/git-annex.log:git-annex version: 10.20220222+git39-gca5834a18-1~ndall+1
handle-result.yaml-6-28b0bfae-success/result-smaug-610/git-annex.log:git-annex version: 10.20220222+git44-gde0c6f08c-1~ndall+1
handle-result.yaml-7-d71c51e3-success/result-smaug-611/git-annex.log:git-annex version: 10.20220222+git53-gb1934cc79-1~ndall+1
handle-result.yaml-8-7b1cb071-success/result-smaug-612/git-annex.log:git-annex version: 10.20220222+git54-gffc17b0b4-1~ndall+1
handle-result.yaml-9-5a6dea48-success/result-smaug-613/git-annex.log:git-annex version: 10.20220222+git58-g801673a39-1~ndall+1

not yet sure if it is worth may be to add some feature to con/tinuous to extract some tokens from the output to be used in the target path names.... feels like an overkill ATM