Skip to content

Generate temporary Gemfile.lock for FOSSA CI scan #1505

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.

Sign up for GitHub

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

Jump to bottom
Open
kaylareopelle opened this issue Apr 25, 2025 · 0 comments
Open

Generate temporary Gemfile.lock for FOSSA CI scan #1505

kaylareopelle opened this issue Apr 25, 2025 · 0 comments

Comments

@kaylareopelle
Copy link
Contributor

FOSSA scans expect a Gemfile.lock to do their work. Gems, as a best practice, do not check in a Gemfile.lock.

The New Relic Ruby agent gets around this by bundling the gem in a step prior to the scan:
https://github.com/newrelic/newrelic-ruby-agent/actions/runs/14669694175/workflow

Something similar may work for this repo, though we'll need to adjust so that all the nested gems get bundled.

Until then, FOSSA scans will fail.

Example: https://github.com/open-telemetry/opentelemetry-ruby-contrib/actions/runs/14674537659
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kaylareopelle