Feature request: Allow concurrent invocations of golangci-lint on separate codebases

[robertlamarre]

Hello,

Pull #812 addressed issue #108, preventing multiple invocations of golangci-lint in parallel. However, we would like to be able to concurrently run multiple instances of golangci-lint validating separate applications. Is there any reason that this couldn't be done by this tool, perhaps by parameterizing the lock file used by the source tree being linted?

Thanks!

[ernado]

Current workaround is to set GOLANGCI_LINT_CACHE (which is path to cache dir) for each application.

[4m3ndy]

Current workaround is to set GOLANGCI_LINT_CACHE (which is path to cache dir) for each application.

Unfortunately this workaround didn't work for us, as we're using a mono-repo for our golang microservices, changing $TMPDIR for each application did the trick

cd $APP_PATH && env -i PATH="$PATH" TMPDIR="$PWD/tmp" golangci-lint -v run ./...

maybe you can try to add --lock-file option to set it through the cli

[SteelPhase]

I'm running into this as well, and it would appear that GOLANGCI_LINT_CACHE does not bypass the lock file check to allow multiple instances

[jirfag]

Hi,
we've implemented the --allow-parallel-runners option in #1070. Cache in one dir should work for multiple runners but I'm not 100% sure, we don't have specific test cases for that.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.