Indeed there was some temporary debug messages and I was hoping that there was a variable we could use from Azure DevOps but apparently not ...

The simplest thing I found was to modify get_commit_message.py to be able to only print the commit message and be used directly in a bash script.

I did not find anything straightforward in the Azure DevOps doc to be able to use a dependency output variable inside a bash script. Let me know if you know of anything.

The only thing I found would be to set a variable in the yaml file from a dependency output like this:

jobs:
- job: A
  steps:
  - bash: |
     echo "##vso[task.setvariable variable=myOutputVar;isoutput=true]this is from job A"
    name: passOutput
- job: B
  dependsOn: A
  variables:
    myVarFromJobA: $[ dependencies.A.outputs['passOutput.myOutputVar'] ]  
  steps:
  - bash: ./my-script.sh
     

My understanding is that inside my-script.sh the dependency output would be available as $MYVARFROMJOBA.

Side-comment by printing the environment, I found out SYSTEM_PULLREQUEST_SOURCECOMMITID could be used to get the commit of the pull request rather than relying on the merge commit message having the commit id as the second word. Quite a minor improvement though ...

SYSTEM_PULLREQUEST_SOURCECOMMITID does not seem documented but it is officially supported see this

OK this seems to be working as expected in my last commit e9e9085. The debian 32bit failure is known and will be tackled in a separate PR.

I'll push a commit with some clean-up and without the [float32] marker, this way the CI will be green.

Side-comment: the posix-docker.yml changes meant for #24201 were actually merged in this PR (probably my fault).

This may break the nightly build until #24198 is merged.