npm renovate fails on azure devops with https 400

[sommmen]

How are you running Renovate?

Self-hosted

If you're self-hosting Renovate, tell us what version of Renovate you run.

@latest (35.134.0 as of writing)

If you're self-hosting Renovate, select which platform you are using.

Azure DevOps (dev.azure.com)

Was this something which used to work for you, and then stopped?

It used to work, and then stopped

Wanted end result.

Hello,

Some time ago i switched renovate to run on my own azure devops hosted agent running windows 10.

Oddly enough renovate works when i run this locally (win10), and on my server, but when i run in in an azure devops pipeline it faults - i cannot for the life of me figure out why.

My build script is as follows;

# Runs the renovate bot on a schedule.
# Adapted from: https://blog.objektkultur.de/how-to-setup-renovate-in-azure-devops/

schedules:
  - cron: "0 5 * * *"
    displayName: "Every day at 7am"
    branches:
      include:
        - main
        - master
    always: true

trigger: none

pool:
  name: 'opg.systems'

variables:
  - group: "renovatebot"

steps:
  - checkout: self
    persistCredentials: true
    fetchDepth: 1
  - task: NodeTool@0
    inputs:
      versionSource: 'spec'
      versionSpec: '18.12.0'
  - script: |
      cd
      git config --global user.email 'bot@renovateapp.com'
      git config --global user.name 'Renovate Bot'
      echo "TOKEN = %TOKEN%"
      echo "GITHUB_COM_TOKEN = %GITHUB_COM_TOKEN%"
      npx renovate@latest
    env:
      TOKEN: '[REDACTED]'
      GITHUB_COM_TOKEN: $(githubtoken)
      LOG_LEVEL: 'debug'
    workingDirectory: '$(Build.SourcesDirectory)'
    displayName: 'Renovate'

Renovate.json

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": [
    "config:base"
  ]
}

config.js

module.exports = {
  platform: 'azure',
  endpoint: 'https://dev.azure.com/[REDACTED]/',
  token: process.env.TOKEN,
  repositories: [
    '[REDACTED]/[REDACTED]'
  ],
  persistRepoData: true
};

Does anybody have any clues or suggestions?

What you tried so far.

• Full scoped access token
• Various configurations, over several days, with various versions of git/node/renovate.
• Different repo, with a clone beforehand and without

Relevant debug logs

Logs

2023-06-20T11:10:40.0060276Z DEBUG: [REDACTED]/[REDACTED] owner = ?owner? (repository=[REDACTED]/[REDACTED])
2023-06-20T11:10:40.0060875Z DEBUG: [REDACTED]/[REDACTED] default branch = master (repository=[REDACTED]/[REDACTED])
2023-06-20T11:10:41.1028767Z DEBUG: Git function thrown (repository=[REDACTED]/[REDACTED])
2023-06-20T11:10:41.1067810Z        "err": {
2023-06-20T11:10:41.1069657Z          "task": {
2023-06-20T11:10:41.1071749Z            "commands": [
2023-06-20T11:10:41.1073023Z              "-c",
2023-06-20T11:10:41.1098409Z              "http.extraheader=AUTHORIZATION: basic **redacted**",
2023-06-20T11:10:41.1100463Z              "ls-remote",
2023-06-20T11:10:41.1101826Z              "--heads",
2023-06-20T11:10:41.1104259Z              "https://**redacted**@dev.azure.com/[REDACTED]/[REDACTED]/_git/[REDACTED]"
2023-06-20T11:10:41.1104661Z            ],
2023-06-20T11:10:41.1105113Z            "format": "utf-8",
2023-06-20T11:10:41.1105334Z            "parser": "[function]"
2023-06-20T11:10:41.1105542Z          },
2023-06-20T11:10:41.1106291Z          "message": "fatal: unable to access 'https://dev.azure.com/[REDACTED]/[REDACTED]/_git/[REDACTED]/': The requested URL returned error: 400\n",
2023-06-20T11:10:41.1111838Z          "stack": "Error: fatal: unable to access 'https://dev.azure.com/[REDACTED]/[REDACTED]/_git/[REDACTED]/': The requested URL returned error: 400\n\n    at Object.action (C:\\Windows\\ServiceProfiles\\NetworkService\\AppData\\Local\\npm-cache\\_npx\\59c0475bfd22776c\\node_modules\\simple-git\\src\\lib\\plugins\\error-detection.plugin.ts:42:29)\n    at PluginStore.exec (C:\\Windows\\ServiceProfiles\\NetworkService\\AppData\\Local\\npm-cache\\_npx\\59c0475bfd22776c\\node_modules\\simple-git\\src\\lib\\plugins\\plugin-store.ts:29:29)\n    at C:\\Windows\\ServiceProfiles\\NetworkService\\AppData\\Local\\npm-cache\\_npx\\59c0475bfd22776c\\node_modules\\simple-git\\src\\lib\\runners\\git-executor-chain.ts:127:42\n    at new Promise (<anonymous>)\n    at GitExecutorChain.handleTaskData (C:\\Windows\\ServiceProfiles\\NetworkService\\AppData\\Local\\npm-cache\\_npx\\59c0475bfd22776c\\node_modules\\simple-git\\src\\lib\\runners\\git-executor-chain.ts:124:14)\n    at GitExecutorChain.<anonymous> (C:\\Windows\\ServiceProfiles\\NetworkService\\AppData\\Local\\npm-cache\\_npx\\59c0475bfd22776c\\node_modules\\simple-git\\src\\lib\\runners\\git-executor-chain.ts:100:40)\n    at Generator.next (<anonymous>)\n    at fulfilled (C:\\Windows\\ServiceProfiles\\NetworkService\\AppData\\Local\\npm-cache\\_npx\\59c0475bfd22776c\\node_modules\\simple-git\\dist\\cjs\\index.js:55:24)\n    at processTicksAndRejections (node:internal/process/task_queues:95:5)"

[rarkins]

I suggest you remove the persistRepoData setting

[sommmen]

Unfortunately i'm receiving the exact same error.

I've tried a couple things, but just getting a 400 somewhere is hard to debug, do you reckon i can add even more logging somewhere?

[rarkins]

It's a git error, and I'm not sure git gives us any additional information than what you see

[viceice]

looks like duplicate auth credentials, one via header and one via url. that maybe causes the 400

[sommmen]

I did some runs and it now seems to work for one pipeline, i presume the persistRepoData was the culprit here.

My other pipeline faulted with 'filename too long' but i forgot to apply core.longpaths on the server.
Both seem to be working now - thanks for your support.