Package-level declarations

Types

Link copied to clipboard
@DisableCachingByDefault(because = "Runs sudo dnf/apt — side-effectful, environment-dependent; caching would give false confidence the toolchain is current.")
abstract class StigInstallDepsTask : DefaultTask

Installs the OS toolchain (LLVM/Z3/clang/cmake) needed to build the analyzer, by running the embedded scripts/setup.sh (sudo dnf/apt). Wraps StigCodeAnalyzerInstaller.installDeps. This is the one sudo-requiring, package-installing step — deliberately separate from the build (StigSetupAnalyzerTask) so the build needs no sudo. Run it once per machine, or in CI provisioning before the build. The build does NOT depend on it (it assumes deps are present and fails clearly otherwise).

Link copied to clipboard
@DisableCachingByDefault(because = "Environment-check task — its results depend on the host (installed tools, distro, libstdc++). Caching would defeat the point of checking.")
abstract class StigSelfTestTask : DefaultTask

Prints stig's toolchain configuration (LLVM major, compiler binaries, compile flags from StigLlvmToolchain). The remaining environment checks (JDK version, Bazel presence, distro + libstdc++ probe, matrix-tests-on-user-machines) land via task #38.

Link copied to clipboard
@DisableCachingByDefault(because = "Builds PhASAR/analyzer into a shared ~/.cache dir. Side-effectful + environment-dependent; cache hits would give false confidence the build is current.")
abstract class StigSetupAnalyzerTask : DefaultTask

Explicit pre-warm / build of the stig-code-analyzer binary on the host machine. Wraps StigCodeAnalyzerInstaller.installAndResolve — idempotent; re-running with unchanged source is cheap (cache hit returns immediately).

Link copied to clipboard
@DisableCachingByDefault(because = "Pure side-effect (println to console); no outputs to cache.")
abstract class StigShowMatrixRankingTask : DefaultTask

Echoes the matrix-test accuracy ranking from a previous test run. Wired as finalizedBy(showMatrixRanking) on the integrationTest task so the ranking surfaces on every run — including when the test task FAILS (which is the common case while iterating on PhASAR limits). finalizedBy runs regardless of success/failure; doLast on the test task itself only runs on success.