All Classes and Interfaces
Class
Description
Logging mechanism for outputting messages to Jenkins build console
Downloads a remote executable into the workspace and returns its path.
A policy control that failed against one or more IaC resources.
Build-page action that renders the IaC scan result as tables (server-side, via the Jelly views).
View model for one severity bucket, exposing the CSS suffix used by the tiles/badges.
First-class Pipeline step for IaC scanning.
Aggregate root of an Infrastructure as Code scan.
A helper class to ensure concurrent jobs don't step on each other's toes.
Deserialized shape of the
sysdig-cli-scanner --iac --output-json report (v1) and its
mapping to the IaCScanResult domain model.High-level information about what was scanned: the source paths and the number of modules,
resources and folders the scanner walked through.
A single IaC resource (e.g.
Wraps the context of a Jenkins run.
A source file the scanner could not parse, along with the details of why it failed.
Provides the Sysdig CLI scanner binary, either by resolving a user-configured
path or by downloading the appropriate release for the current OS/arch.
Runs the Sysdig CLI scanner binary and returns its raw JSON output.
Holds the folder hierarchy used by a single scanner execution.
Resolves which version of the Sysdig CLI scanner should be used, honoring the
custom version configured by the user and falling back to a pinned version.
Severities are declared from most to least severe;
Severity.values() therefore already yields a
ranked order.Sysdig Secure plugin results for a given build are stored and subsequently retrieved from an instance of this class.
A source file containing resource kinds the scanner does not (yet) support, along with the list
of those unsupported resource kinds.