Gradle

Gradle is a build automation CLI that executes project-defined tasks and ships built-in commands for dependency inspection, reporting, wrapper management, and build initialization. It is used to build, test, package, and publish software across Java, Kotlin, Android, native, and other polyglot projects.

• Run project build, test, lint, packaging, and publishing tasks from the terminal, including multi-project builds through task selectors and project paths.
• Inspect project structure, task availability, properties, dependency graphs, selected versions, outgoing variants, and resolvable configurations before changing build logic.
• Initialize new builds, generate or update the Gradle Wrapper, and control execution with dry runs, build cache, configuration cache, parallelism, continuous mode, and daemon flags.

• Commands are explicit, mostly non-interactive, and built around task names, flags, exit codes, and project directories, which fits CI and agent loops well.
• Inspection is strong, but most built-in output is plain text or HTML reports rather than JSON, so follow-up parsing is less reliable than with more machine-oriented CLIs.
• Best fit when an agent already has repo context and can drive gradlew inside a specific project; usefulness drops outside a concrete build with known tasks and plugins.

• Most useful actions depend on repository-local build scripts, plugins, credentials, and JDK or toolchain setup, so behavior varies sharply across projects.
• Runs can start daemons, download distributions through the wrapper, and execute project or plugin code, which adds side effects and trust concerns for unattended use.