Skip to content
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

The UpdateCli step fails regularly when processing jenkins.io PRs #3958

Open
jmMeessen opened this issue Feb 23, 2024 · 1 comment
Open

The UpdateCli step fails regularly when processing jenkins.io PRs #3958

jmMeessen opened this issue Feb 23, 2024 · 1 comment

Comments

@jmMeessen
Copy link

jmMeessen commented Feb 23, 2024

Service(s)

ci.jenkins.io

Summary

The updateCli step fails when building a www.jenkins.io PR with the following error:

alpineLatestVersion
-------------------
ERROR: 	API rate limit exceeded for installation ID 8286021.
ERROR: ✗ searching GitHub release: API rate limit exceeded for installation ID 8286021.
ERROR: {Get the latest Alpine Linux version ✗   { {  } }   ERROR: 	API rate limit exceeded for installation ID 8286021.
ERROR: ✗ searching GitHub release: API rate limit exceeded for installation ID 8286021.
} searching GitHub release: API rate limit exceeded for installation ID 8286021.
Pipeline "Bumps the ruby docker images versions in the documentation" failed
Skipping due to:
	sources stage:	"template: cfg:5:88: executing \"cfg\" at <source \"alpineLatestVersion\">: error calling source: parent source \"alpineLatestVersion\" failed"

Reproduction steps

No response

@jmMeessen jmMeessen added the triage Incoming issues that need review label Feb 23, 2024
@lemeurherve
Copy link
Member

lemeurherve commented Feb 27, 2024

This issue concerns all GitHub Actions across @jenkins-infra organisation and most of our Jenkins instances.

We need to add more GitHub applications and distribute the load amongst them to avoid being rate limited.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants