Troubleshooting

This page stays as a quick maintainer-facing checklist. Detailed contract and authoring rules live elsewhere.

Discovery Fails

Check:

divekit plugin source list
divekit plugin discover --verbose

Verify:

• the source is configured and trusted
• ci.yaml exists, or ci.yml exists as the compatibility fallback
• plugin.json exists and is valid

Plugin Does Not Run

Check:

divekit plugin list --verbose

Verify:

• the plugin is enabled
• the selected source, project, and ref are correct
• evaluation-pipeline templates were injected with divekit plugin install
• the job uses the plugin image built for the selected release tag
• the Dockerfile copies implementation files from src/ into the path used by ci.yaml
• plugin scripts use DIVEKIT_PLUGIN_DIR only for optional materialized assets such as feedback/

Example:

script:
  - python /opt/divekit/src/main.py

Report Data Is Missing

Verify that the child pipeline publishes:

• plugin-results/<plugin-id>/report.json

Common causes:

• wrong plugin ID or wrong output path
• artifacts do not include plugin-results/...
• plugin writes plugin-specific files but never emits normalized report.json

Feedback Is Missing From Pages

Verify that the child pipeline publishes one of:

• plugin-results/<plugin-id>/feedback.md
• plugin-results/<plugin-id>/feedback/index.json
• plugin-results/<plugin-id>/feedback/**/*.md

Feedback is only shown on the generated GitLab Page and in public/feedback.json. It is not written back to work repositories.

Build Or Plugin Execution Failed

Do not model build or plugin execution problems as fake tests. Publish an issue artifact instead:

• plugin-results/<plugin-id>/issues/index.json
• plugin-results/<plugin-id>/issues/<issue>.md
• plugin-results/<plugin-id>/logs/<tool>.log

Set affectsResult: true for issues that mean the evaluation could not complete successfully. The generated GitLab Page shows those issues in a separate execution-problems section and writes the machine-readable data to public/issues.json.

Wrong Plugin Version Or Repository Is Used

Re-pin the ref, or reselect the repository if the plugin should come from a different repo:

divekit plugin pin <plugin-id> <tag>
divekit plugin add <plugin-id> --project <group>/<repo> --ref <tag>
divekit plugin refresh

Source Or Permission Errors

Verify:

1. the host alias exists
2. authentication is configured with divekit auth
3. the source was added with --trusted