glab dependency-firewall gradle

Run Gradle through the GitLab Dependency Firewall. (BETA)

Synopsis

Run the Gradle binary through the GitLab Dependency Firewall. The command checks each package download and upload against the policy for the current project, refuses blocked packages, and summarizes the results after the run.

The command uses your package manager’s registry or index configuration, and does not modify it.

The command runs gradle from your PATH. The Gradle Wrapper (./gradlew) is not supported.

Gradle does not download artifacts already cached in ~/.gradle/caches/, so the firewall does not check them. Clear the cache to check them again.

All arguments are forwarded to gradle verbatim.

This feature is in beta and might not be ready for production use. It might be unstable and breaking changes can occur outside of major releases. For more information, see https://docs.gitlab.com/policy/development_stages_support/.

glab dependency-firewall gradle <gradle args> [flags]

Examples

console
# Build a project through the Dependency Firewall
glab dependency-firewall gradle build

# List dependencies through the Dependency Firewall
glab dependency-firewall gradle dependencies

Environment variables

HTTPS_PROXY: outbound proxy glab uses to reach package registries. Credentials in the URL are sent to the proxy.
NO_PROXY: hosts glab reaches directly instead of through HTTPS_PROXY.

Options inherited from parent commands

  -h, --help   Show help for this command.