These diagrams come from Gradle's resolved Task.taskDependencies after applying and configuring the STIG plugin. They include dependencies carried by task-backed input providers, not just explicit dependsOn declarations. No task actions run during generation.
An arrow points from a prerequisite to its dependent. It does not specify a total execution order. Ordering constraints (mustRunAfter and shouldRunAfter) and finalizedBy are not prerequisite edges and are not shown. Caching, onlyIf, and execution-time checks can skip task actions without removing their registered prerequisites. Statically disabled tasks are marked in the diagrams. Each view uses a separate reference build with the named task selected before plugin configuration, so invocation-dependent wiring, such as root aggregation and the configuration writer, is respected.
The reference build contains a root and one :element activity. It enables specification import, a generated analysis harness, data/control-flow analysis, and cascading-failures analysis; it selects one native target and one source compilation unit. These settings expose the optional pipeline branches. A consumer's enabled features, selected tasks, and included builds can change its effective graph. The diagrams describe this configured reference build, not a captured consumer execution.
See STIG workflows for task intent and the task API for options. Regenerate this page from the STIG source root:
The output is stig-codex-plugin/build/generated/references/specifications/configuration-and-gradle/gradle-task-graph.md. Writerside and the Codex plugin package this same generated Markdown.
Overview
This compact view selects the main producers and report gates from the activity report graph. Arrows represent prerequisite paths: intermediate tasks and transitively implied links are omitted. Labels split the registered task names into words. The following detailed views retain direct dependencies.
Root report
Element tasks are leaves in this view; their prerequisites are expanded below.
Activity report
Prerequisites of :element:stigGenerateHtml with source analysis enabled. Model import is a separate source-editing invocation.
Analysis configuration
Prerequisites of :element:stigConfigureAnalysis. Run this configuration writer alone, then use a new Gradle invocation to check the changed build scripts.
Configuration-only checking
Prerequisites of :element:stigCheckAnalysis --configuration-only.
Full analysis collection
Direct prerequisites of :element:stigCheckAnalysis without --configuration-only. The report and configuration prerequisites are expanded in the preceding views.