Repository limit and concurrency

[emirot]

Hey there,

Let's say I'm on a private gitlab with more than 4000 repositories, it looks like it will take a long time to run renovatebot on every repo. I've just tried on 4 repos it took 5min with a runner with a decent runner more than 4Gb and 1 core.
Is there a way to use some concurrency ?
I was wondering if we could break up the repo list into multiple sublists and have different schedules take care of that.

[rarkins]

You could run several in parallel and use non overlapping autodiscoverFilter configs on each.

[rarkins]

Yes, the typical way is that users "invite" your @renovate-bot account into individual repos or groups they want it to onboard. GitLab doesn't require any approval step for that so the bot essentially just starts working on the repo(s) once that's done.

If you have multiple security domains within the company, please make sure you're aware of how GitLab's pipeline security works and its limitations: https://docs.renovatebot.com/gitlab-bot-security/

FYI a colleague of yours "Nathan B" (I assume that's enough info for you to work out who I mean) already requested a license key some time ago so he may already have an instance running within the same company.

[emirot]

@rarkins thanks I will try to create the @renovate-bot account.
I received an email with the license key and it create the first initialization MR in my repo.
but since then it doesn't work Is there any kind of state in whitesource/renovate:1.2.0 ?
I see in the log

"ERROR: Repository has unknown error (repository=nolane/test-renovate)\n

I don't see the MR that should update the deps created.

[rarkins]

Configure LOG_LEVEL=debug in env and restart

The /status endpoint may help too

[emirot]

@rarkins
I've added LOG_LEVEL=debug
but unfortunately I don't have direct kubectl access.
I was able to get from someone:

 "task": {
           "concatStdErr": false,
           "format": "utf-8",
           "commands": [
             "ls-remote",
             "--heads",
             "https://oauth2:**redacted**@gitlab.sandbox.company.net/nolane/hack-week-renovatebot-2.git"
           ]
         },
         "message": "fatal: unable to access 'https://gitlab.sandbox.company.net/nolane/hack-week-renovatebot-2.git/': gnutls_handshake() failed: An unexpected TLS packet was received.\n",
         "stack": "Error: fatal: unable to access 'https://gitlab.sandbox.company.net/nolane/hack-week-renovatebot-2.git/': gnutls_handshake() failed: An unexpected TLS packet was received.\n\n    at GitExecutorChain.onFatalException (/usr/src/app/node_modules/simple-git/src/lib/runners/git-executor-chain.js:60:87)\n    at GitExecutorChain.<anonymous> (/usr/src/app/node_modules/simple-git/src/lib/runners/git-executor-chain.js:51:28)\n    at Generator.throw (<anonymous>)\n    at rejected (/usr/src/app/node_modules/simple-git/src/lib/runners/git-executor-chain.js:6:65)\n    at processTicksAndRejections (internal/process/task_queues.js:93:5)"

It worked yesterday creating a MR weird.

[emirot]

I switched the GIT_SSL env var and it looks to work!