-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kubernetes@V1 - Fails to query GitHub API #9794
Comments
Can confirm that this has nothing to do with Github, this is 100% a task problem.
The command being run is:
Here's the same issue in a different thread: |
@damienwebdev If you do not have system.debug set to true, the task will not show you that it's querying github API. Every time we get this failure and have debug logs enabled, this github call appears before it. |
@xenalite, ah I see. Really good catch there. I'm assuming that this must be Azure Pipelines reaching the Github API rate limit for that particular query... which I now realise you already discovered. |
@xenalite I think I have a short-fix while MSFT attempts to solve this long term... there's two issues at hand: Issues
In my case, my settings look like: Notice that in the SolutionsSolution for problem 1Rework the underlying functionality to handle the rate-limiting. An internal MSFT dev should most likely do this, or a willing contributor familiar with the project. Solution for problem 2Remove the |
@damienwebdev My task doesn't even have a version drop down or the advanced section, because I only every do login and logout commands. |
we have fixed this issue and deployed. this should no more be problamatic. |
Environment
Server - Azure Pipelines
Agent - Private:
Issue Description
We are using V1 of Kubernetes task. Some days this task fails when we have too many builds / releases in a time period. The Kubectl command being run does not make a difference.
The command attempts to look for latest release of kubectl. This is despite:
It does not seem to handle bad output from the Github API. After sending a GET to this URL above right after the failure, it turns out we hit an API request quota for unauthenticated requests. As an organization we have a single outbound IP address, so that contributes to the problem. Too many builds in 1 team project will fail another team's builds / releases and vice-versa.
Task logs
Error logs
The text was updated successfully, but these errors were encountered: