jfrog / jfrog/jfrog-cli

add filter option for non-runtime dependencies from buildinfo

Open
#3,369 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
Go
Stars
595
Forks
307
Avg merge
4d 17h
Merged PRs (30d)
17

Description

Is your feature request related to a problem? Please describe.

The build integrations currently collect dependencies from all scopes. For compliance only runtime dependencies are of interest since dev and test dependencies are not part of production software.

We thus need to filter out any dependencies that are not present at runtime.

Describe the solution you'd like to see

We want an option to either only collect runtime dependencies, or to filter any non runtime scoped dependencies out of builds before publishing.

Describe alternatives you've considered

We currently filter those non runtime dependencies ourselves from the local buildinfo files after they are created and before they are uploaded.

Additional context

See also
https://github.com/jfrog/jfrog-cli/issues/3368

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the build integrations that collect dependencies from buildinfo and inspect how local buildinfo files are prepared before upload. Define how runtime-scoped filtering should be exposed and verify that published builds exclude non-runtime dependencies while preserving current behavior by default.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
build-system, cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.