IDE Integrations
JetBrains IDEs
Overview
The JetBrains plugin supports Java and Kotlin teams with run history panel, failure navigation, and CLI task integration for Gradle/Maven pipelines.
Enterprise Java teams use this for parity between IDE workflows and CI pipelines invoking zof CLI.
Who should read this
- QA engineers, SREs, platform teams, and developers operating Zof Console and APIs.
When to use this workflow
- Onboarding new team members to Zof terminology and workflows
- Authoring internal runbooks aligned with Console labels
- Designing CI/CD or webhook integrations against documented behavior
Step-by-step procedure
Install plugin
Settings → Plugins → Marketplace → Zof AI → Install.
Restart IDE after install completes.
Configure credentials
Settings → Tools → Zof → API key from environment or staging vault.
Set default project ID from Console project settings.
Gradle task
Add exec task running zof run --wait --env staging.
Wire ZOF_API_KEY via CI secrets in pipeline, not build files.
Key concepts
- Organization scope
- All Zof Console and API operations are isolated to your authenticated tenant.
- Governed execution
- Agent output and remediation follow policy packs with human approval when configured.
Best practices
- Use same project ID in plugin and Gradle task
- Run staging validation before merge to main
Was this page helpful?
