Plugin Development

This section is now an orientation page. The plugin documentation is intentionally split to reduce drift:

• user-facing setup stays in Quick Start / Plugins
• CLI command behavior stays in the generated CLI Commands reference
• maintainer-facing semantic contract belongs in the Divekit CLI repository
• plugin authoring and CI conventions belong in the plugin template repository
• plugin-specific CLI configuration can be exposed through Configuration Wizards

Split

User-facing setup

• discover plugins
• choose a source and pin a ref
• enable or disable them per distribution
• update injected templates

Use:

• Plugins
• CLI Commands

Maintainer-facing contract

• discovery through manifest.json, with kind plugin-suite for a builder and plugin for a plugin
• one job.yaml per repository that contributes a pipeline job; the CLI composes the job into the evaluation pipeline
• suite pins and the per-course locks in .divekit/eval-pipeline/plugins.json, sources in plugin-sources.json
• optional materialized feedback assets under feedback/; plugin code ships in the plugin image
• normalized reporting through plugin-results/<suite>/<plugin>/report.json
• optional feedback, execution issue, and html artifacts under plugin-results/<suite>/<plugin>/
• declarative configuration wizards declared in manifest.json

See:

• Contract Reference
• Configuration Wizards
• CLI Plugin Contract

Authoring and CI conventions

• repository layout: manifest.json, job.yaml, Dockerfile, code under src/
• image structure, derived from the suite’s build image
• release-template usage
• the DIVEKIT_PLUGIN_RESULT_DIR, DIVEKIT_SUITE_ID, and DIVEKIT_PLUGIN_ID variables a job receives
• FAQ artifact conventions
• execution issue artifact conventions
• copyable examples for new plugin repos

See:

• Authoring Guide
• Troubleshooting
• Plugin Template README

Practical Rule

If you are using plugins, stay in Quick Start and CLI reference. If you are building or maintaining plugins, use the maintainer-facing docs and template repository instead of treating this pages section as the primary source of truth.