// Local build and test ergonomics for Cloudbreak—Gradle commands, module-scoped tests, checkstyle, and how they relate to GitHub Actions PR workflows.
Official CDP Public Cloud documentation lookup. Use this skill when any agent (Developer, Architect, Reviewer) needs to verify official Cloudera requirements, release notes, or API specifications for the Public Cloud.
Operate read-first against AWS, Azure, and optionally GCP from the terminal or cloud MCP tools—instances by region, related compute/network resources, and troubleshooting. For Cloudbreak work in cloud-aws-*, cloud-azure, cloud-gcp modules.
Use GitHub (via MCP) for Cloudbreak PRs, checks, and diffs from the editor. Pairs with cb-reviewer for standards and cb-triage/cb-junior-dev for ticket context.
Senior-level thoroughness for Jira ticket resolution in the Cloudbreak project. Use this skill to fetch a Jira ticket, research related Confluence documentation, analyze the root cause, create reproduction tests, implement fixes, and prepare a high-quality PR.
Turn a Jira issue into an actionable engineering plan for Cloudbreak—without implementing code. Use this skill for fast triage, scope discovery, and verification checklists using Atlassian MCP, Confluence (CB Engineering Home), and local repo inspection.
Governance and architectural standards for the Cloudbreak project. Use this skill to understand directory structures, coding guidelines, commit message rules, and API design principles.
| name | cb-ci-local |
| description | Local build and test ergonomics for Cloudbreak—Gradle commands, module-scoped tests, checkstyle, and how they relate to GitHub Actions PR workflows. |
Use this skill to mirror PR CI locally before push, or to debug failures quickly. Java 21, Gradle, Spring Boot 3.3 per root GEMINI.md.
| Action | Command |
|---|---|
| Clean build (full, heavy) | ./gradlew clean build |
| Module unit tests (preferred during dev) | ./gradlew :<module>:test |
| Single test class | ./gradlew :<module>:test --tests com.example.FullClassName |
| Single test method | ./gradlew :<module>:test --tests com.example.ClassName.methodName |
| Checkstyle (when enabled for module) | ./gradlew :<module>:checkstyleMain and/or checkstyleTest |
Replace <module> with the Gradle project name (directory name for most modules: core, datalake, environment, integration-test, etc.).
GEMINI.md (“Logical Domain Mapping”).<module>/GEMINI.md when present before large test runs.config/checkstyle/checkstyle.xml (applied from root build.gradle)../gradlew :foo:checkstyleMain is not found, run ./gradlew tasks --group=verification in that module or use root aggregate tasks if your branch defines them..github/workflows/pull-request.yaml runs on pull_request and includes Jira update and unit test jobs (and others as defined in the file)../gradlew :<module>:test is the fastest way to match “unit test failed in CI” for a specific module before re-pushing.integration-test module is separate from per-module unit tests; it has its own README and setup (see integration-test/README.md for local env, UMS, and long-running scenarios).integration-test runs in every developer’s default loop unless the ticket requires it.--tests narrowed; check for timing, shared state, or missing mocks in the failing module’s src/test/java.org.gradle.jvmargs in gradle.properties); prefer fixing leaks or oversized fixtures.README.md / README-devnotes.md credentials in ~/.gradle/gradle.properties.cb-junior-dev — Repro test first; then full :module:test before PR.cb-developer — After tests pass, run janitorial checks if you touched style-sensitive areas.