You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If too many jobs in our test suite use @terascope/fetch-github-release to download assets at the same time our github account gets rate-limited, causing the test job to fail.
We could do a couple of things:
cache the assets in github in an automated workflow(daily?) and pull from the cache in each job
run one job at the start of each workflow run that pulls assets and passes them into all the jobs that need them
The text was updated successfully, but these errors were encountered:
Does fetch-github-release have a local caching mechanism?
No it doesn't. I don't believe this would help in CI since all jobs run in separate runners, so they all have their own instance of fetch-github-release
If too many jobs in our test suite use
@terascope/fetch-github-release
to download assets at the same time our github account gets rate-limited, causing the test job to fail.We could do a couple of things:
The text was updated successfully, but these errors were encountered: