ls-remote failing after automerge on Bitbucket – could not read Username – No such device or address #42210
Replies: 1 comment 1 reply
-
|
That's presumably because a duplicate Now the issue is that after automerge succeeds (for which it used the credentials from Bitbucket then rejects the duplicate header and falls back to username/password auth, which in your case is the credential helper that tries to read from stdin. I guess that the error causes the stored credentials to be removed from the keychain. To verify this hypothesis, you could copy this cleanup block: renovate/lib/workers/repository/index.ts Lines 191 to 197 in 91049f0 directly after the renovate/lib/workers/repository/index.ts Lines 158 to 160 in 91049f0 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
How are you running Renovate?
Self-hosted Renovate CLI
Which platform you running Renovate on?
Other (please specify)
Which version of Renovate are you using?
42.15.0, 42.99.0 & 43.96.0 (but on Node 22)
Please tell us more about your question or problem
I am trying to implement automerge for some patch versions of our parent poms on Bitbucket, with Renovate CLI running on Jenkins. I have tried with Renovate 42.15.0 and 42.99.0 (we don’t have Node 24 on our Jenkins¹). I am only trying on a personal repository for now.
Everything works properly, PRs are created when
automerge: falseor when a build fails ("automergeType": "branch"). However, after automerging (which works fine), it saysRestarting repository job after automerge resultand then tries to do anls-remote, which seems to have the proper header, but it fails regardless withStrangely, this
ls-remoteonly seems to happen after an automerge. I guess it’s not needed for the initial clone?AFAICT the
ls-remoteURL is correct, and I can execute the command locally just fine (without theBearer).I also tried with a host rule
{"hostType": "bitbucket-server", "token": "{{ secrets.BITBUCKET_TOKEN }}"}(withsecrets.BITBUCKET_TOKEN: process.env.RENOVATE_TOKEN) but that did not help.In local (macOS 15), it works with username and password, but then the
fetchBranchCommits()line contains**redacted**@in the URL. With token it fails in the same way as on Jenkins, and even stranger: it appears to remove my credentials from osxkeychain! (only in case of automerge)I’m including the logs from the automerging until the error, as well as a simplified version of the printed combined config (I essentially removed
onboardingConfig,ignorePresetsand the non-automergepackageRules)¹ I actually tried 43.96.0 on Node 22, and despite complaining about the unsupported version, it ran regardless and produced the same error
Logs (if relevant)
Logs: Combined config
Logs: automerge and failure
Beta Was this translation helpful? Give feedback.
All reactions