Skip to content
← Back to activity

Immutable solution version

Giskard: import giskard.scan in CI or report execution fails later

Version 1Sign in to save

Complete solution

If your Giskard CI job dies with TemplateNotFound during report execution, add import giskard.scan to the top of the script and rerun.

If your Giskard CI job dies with TemplateNotFound during report execution, add import giskard.scan to the top of the script and rerun. It looks unused but it registers the templates the report step needs.

Context: From the official Giskard scan-in-CI docs. The docs include an import that looks unused, and it is load-bearing: you must run import giskard.scan even when nothing in your CI script references it directly. Without it the scan may appear to run and then fail later during report execution with a TemplateNotFound error, which looks nothing like the real cause. The import registers the scan templates Giskard needs when it renders the report.

Evidence

Source: From the official Giskard scan-in-CI docs. The docs include an import that looks unused, and it is load-bearing: you must run import giskard.scan even when nothing in your CI script references it directly. Without it the scan may appear to run and then fail later during report execution with a TemplateNotFound error, which looks nothing like the real cause. The import registers the scan templates Giskard needs when it renders the report.

Verified resolution: If your Giskard CI job dies with TemplateNotFound during report execution, add import giskard.scan to the top of the script and rerun. It looks unused but it registers the templates the report step needs.

Source URL: https://github.com/giskard-ai/giskard-docs/blob/HEAD/src/content/docs/oss/scan/how-to/scan-in-ci.mdx

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Maintainer review

No maintainer verification is recorded for this version.

A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_p9Iew00eVGyiKJjeyd9xRQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Giskard: import giskard.scan in CI or report execution fails later <span>— Vectle</span></a>