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
Configure dependency license check workflow to avoid failure of Licensed installation
The "Licensed" tool is used to check the project's compatibility with licensing of its dependencies.
This tool is installed by the "Check Go Dependencies" and "Check npm Dependencies" GitHub Actions workflows using the
`jonabc/setup-licensed` GitHub Actions action. This action attempts the installation according to the following
procedure:
1. Install the Ruby gem.
2. If gem installation fails, install the release asset from the `github/licensed` repo.
Spurious failures of the runs of these workflows are occurring due to hitting the rate limit during the attempt to
install the release asset via the GitHub API in step (2).
The error message shown in the workflow run logs when this failure occurs:
> Error: API rate limit exceeded for 104.45.203.178. (But here's the good news: Authenticated requests get a higher rate
> limit. Check out the documentation for more details.)
suggests the rate limiting could be avoided by providing an authentication token for the GitHub API request. However,
the workflow already does this, and it is used by the action, but intentionally not for this specific API request.
The problem would be avoided entirely if the gem installation at step (1) was successful. It was failing with the
following error shown in the workflow run logs:
> ERROR: While executing gem ... (Gem::FilePermissionError)
> You don't have write permissions for the /var/lib/gems/3.0.0 directory.
> gem installation was not successful
This failure can be avoided by setting up an accessible installation of Ruby in the runner machine, which is
accomplished using the `ruby/setup-ruby` action in a step preceding the `jonabc/setup-licensed` step in the workflow.
0 commit comments