The output from the pipeline job that fails on a node is:

using credential 6e96f729-8440-40bf-8710-88689c791d3b
Cloning the remote Git repository
Cloning repository https://code.office.carallon.com/pharos/magpie
> C:\Program Files\Git\bin\git.exe init c:\jenkins\workspace\magpie-verify_01_8301_2 # timeout=10
Fetching upstream changes from https://code.office.carallon.com/pharos/magpie
> C:\Program Files\Git\bin\git.exe --version # timeout=10
using GIT_ASKPASS to set credentials
> C:\Program Files\Git\bin\git.exe fetch --tags --force --progress – https://code.office.carallon.com/pharos/magpie +refs/heads/:refs/remotes/origin/ # timeout=10
> C:\Program Files\Git\bin\git.exe config remote.origin.url https://code.office.carallon.com/pharos/magpie # timeout=10
> C:\Program Files\Git\bin\git.exe config --add remote.origin.fetch +refs/heads/:refs/remotes/origin/ # timeout=10
> C:\Program Files\Git\bin\git.exe config remote.origin.url https://code.office.carallon.com/pharos/magpie # timeout=10
Fetching upstream changes from https://code.office.carallon.com/pharos/magpie
using GIT_ASKPASS to set credentials
> C:\Program Files\Git\bin\git.exe fetch --tags --force --progress – https://code.office.carallon.com/pharos/magpie refs/changes/01/8301/2:refs/remotes/origin/01/8301/2 # timeout=10
Checking out Revision 787879583e36f6e3afc5b60d35d15409d2c6a11a (refs/remotes/origin/01/8301/2)
> C:\Program Files\Git\bin\git.exe rev-parse "01/8301/2^

" # timeout=10
> C:\Program Files\Git\bin\git.exe config core.sparsecheckout # timeout=10
> C:\Program Files\Git\bin\git.exe checkout -f 787879583e36f6e3afc5b60d35d15409d2c6a11a # timeout=10
ERROR: Timeout after 10 minutes
 

Have you checked which credentials are used and what are the ones you were expecting to use?

I believe I am using the correct stored credentials, they work fine if I downgrade the module to 0.3.5.

They are https username and password that work everywhere else. Do they need to be something special?

So looking at this some more, I believe it is the LFS Pull step that is using the wrong credentials. For some reason it previously used to say 'Enabling Git LFS pull' before it started this and did the config core.sparsecheckout.

I've uploaded a fix for this issue to GerritHub.

https://review.gerrithub.io/c/jenkinsci/gerrit-code-review-plugin/+/477949

Thanks nickb_carallon looking at your fix right now.

Unfortunately, your fix is breaking existing functionality.

Let me reproduce the problem and see if there is another way to achieve the same result.

I just tried and it works for me. When the build is triggered on a remote host, I see:

using GIT_ASKPASS to set credentials jenkins-at-gerritci

In your case I see from your logs:

using GIT_ASKPASS to set credentials

Did you set the credentials id on the multi-branch pipeline job?