Skip to content

Receiving a number of HTTP 429 errors when fetching the release from GitHub #31

Open
@diosif-cr

Description

Hello,

Thank you for your work regarding XEOL and this GitHub Action. We've added it to our release pipeline, scanning our Docker images before they're pushed to ECR.

We have a monorepo with 13 projects, each of which, depending on the changes made in individual PRs, could build a Docker image and trigger an XEOL scan. We're also a fairly active team with multiple merges to main in a day. All of this results in us triggering, at times, 13 XEOL scans in parallel, potentially many times a day.

We're seeing the following issue sporadically during the day:

Run xeol-io/xeol-action@v1.0.7
  with:
    image: xxx.dkr.ecr.eu-west-1.amazonaws.com/xxx/hello-api:1.2.3
    fail-build: true
    output-format: table
  env:
    [...]
/usr/bin/chmod +x /home/runner/_work/_temp/09987f0d-35f8-4405-8741-dbbda5279b42
/home/runner/_work/_temp/09987f0d-35f8-4405-8741-dbbda5279b42 -b /home/runner/_work/_temp/09987f0d-35f8-4405-8741-dbbda5279b42_xeol v0.9.3
[info] checking github for release tag='v0.9.3' 
Error:  received HTTP status=429 for url='https://github.com/xeol-io/xeol/releases/v0.9.3' 
Error:  unable to find tag='' 
Error:  do not specify a version or select a valid version from https://github.com/xeol-io/xeol/releases 
Error: ENOENT: no such file or directory, stat '/home/runner/_work/_temp/09987f0d-35f8-4405-8741-dbbda5279b42_xeol/xeol'

Any advice on how we can get around this, please?

I assume it's an issue with GitHub rate-limiting us, but I'm not clear on how to bypass this limit.

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions