glab(1)

πŸ“¦
version 1.128.0 Β· 2 versions
, in arch rolling

πŸ’… glab(1) β€” the manual, but make it make sense

okay so this is the glab manual page, bestie, and today we're specifically covering glab-dependency-firewall-gradle πŸŽ€ β€” yes the whole long name, it's giving "my mom named me after both grandmas" energy but we move.


✨ NAME ✨

glab-dependency-firewall-gradle β€” run Gradle through the GitLab Dependency Firewall. 🧱πŸ”₯

🫢 heads up: this one is BETA. More on that in a sec, don't @ me yet.

🌸 SYNOPSIS 🌸

glab dependency-firewall gradle  [flags]

literally that's it. type it, love it, flags optional πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

okay so picture this: you run the Gradle binary through the GitLab Dependency Firewall. every single package download and upload gets vibe-checked against the policy for the current project πŸ‘‘ β€” blocked packages get a hard no and a refusal, and after the whole run finishes you get a lil summary of what went down. iconic behaviour tbh.

it uses your package manager's registry or index configuration and β€” this is the respectful part β€” does not modify it. hands off. we don't touch. πŸ™ˆ

it runs gradle straight from your PATH. and no, the Gradle Wrapper (./gradlew) is not supported, so don't even try it, that's not the moment πŸ’€

now here's the tea β˜• β€” Gradle does <strong>not</strong> download artifacts that are already cached in ~/.gradle/caches/, so the firewall does <strong>not</strong> check those. if you want them checked again, clear the cache. that's the whole trick, no cap.

all arguments get forwarded to gradle verbatim β€” like, word for word, we are not touching them, we are not editing them, we are simply passing the message along 🫑

⚠️ beta warning!! 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 😭 which is very much giving chaos. for more information, see https://docs.gitlab.com/policy/development_stages_support/ β€” go read it, i'll wait πŸ“

πŸ’– OPTIONS INHERITED FROM PARENT COMMANDS πŸ’–

these aren't even ours, we just inherited them like a weird family heirloom:

  • -h, --help[=false] β€” show help for this command. classic, reliable, always there for you ⭐

🌈 EXAMPLE 🌈

build a project through the Dependency Firewall

glab dependency-firewall gradle build

list dependencies through the Dependency Firewall

glab dependency-firewall gradle dependencies

look at that. two examples. both slaying. πŸ”₯


🧚 SEE ALSO 🧚


and that's the page!! auto generated by spf13/cobra, dated Nov 2026, and it's all sitting here in glab(1) πŸŽ€βœ¨ go forth and firewall responsibly, bestie πŸ’œ

πŸ“¦ where this page comes from