We were using an on premise Jenkins against an on premise GitBlit. This worked fine. Last week we migrated from GitBlit to Azure DevOps.
Our Jenkins Jobs now run with the PAT of a 'fake' Azure Account (not the 'Build Service Account' because that one can't be used by an on premise Jenkins). So for Azure DevOps this is a regular user. We found no other way to set this up. Using the PAT of an employee was not really a good option.
Problem now is that we are constantly hitting the Rate Limites with following error:
Request was blocked due to exceeding usage of resource 'ATCPU' in namespace 'VSID'. For more information on why your request was blocked, see the topic "Rate limits" on the Microsoft Web site (https://go.microsoft.com/fwlink/?LinkId=823950).
After which the Jenkins Job fails.
This is a game stopper in our migration to Azure DevOps because there seems to be no way to adjust those Rate limits for a given user...
Do you have recommendations? Is there a way to increase those limits?
In the screenshot, what does the Count and TSTUs exactly mean? We have the idea that it's not about how many bytes are transferred but rather the number of Git Operations.
Our Jenkins Jobs mainly clone Git Repositories with the usage of local mirrors.