glab dependency-firewall maven

Run Maven through the GitLab Dependency Firewall. (BETA)

Synopsis

Run the Maven binary (mvn) 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 checks .jar, .pom, .aar, and .war files, including timestamped snapshot files. It does not check checksum and signature files (.md5, .sha1, .sha256, .sha512, and .asc).

The command runs mvn from your PATH. The Maven Wrapper (./mvnw) is not supported.

Maven does not download artifacts already cached in ~/.m2/repository/, so the firewall does not check them. Clear the cache to check them again.

All arguments are forwarded to mvn 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 maven <mvn args> [flags]

Examples

console
# Build a project through the Dependency Firewall
glab dependency-firewall maven verify

# Resolve dependencies through the Dependency Firewall
glab dependency-firewall maven dependency:resolve

# Deploy a project through the Dependency Firewall
glab dependency-firewall maven deploy

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.