We’re seeing a 502 error for every 10-15(at random) git commands executed that access Gitlab.com repositories.
We expect to not see those errors, and being able to execute git commands without this problems. We’re working with hundreds of repositories right now on gitlab and this is affecting our jenkins builds.
All this commands and errors are happening when executing “git ls-remote” and “git clone” on Gitlab.com repositories we’ve access to.
As of now, we’ve been troubleshooting our jenkins nodes for possible problems related to those 502 errors, but we’ve found no cause of this on our side.