Glossary
Short definitions for recurring Terrabuild terms.
| Term | Definition | See Also |
|---|---|---|
| Action | An operation exposed by an extension, such as build, test, or publish. | Extensions |
| Artifact | Files captured after a target runs and stored in cache. | Project Block, Target Block |
| Cluster | A set of compatible tasks grouped into one batch build. | Batch Builds |
| Command | One action invocation inside a target, for example @dotnet build { }. | Syntax |
| DAG | The directed acyclic graph Terrabuild uses to model tasks and dependencies. | Graph |
| Dependency | A relationship that affects build order or rebuild propagation. | Workspace Target Block, Project Block |
| Extension | A built-in or custom capability provider such as @dotnet or @docker. | Extensibility, Workspace Extension Block |
| Hash | The deterministic value used as the cache key for a task. | Caching |
| Insights | The managed backend used for shared Terrabuild cache storage. | Usage |
| Node | A task represented in the build graph. | Graph |
| Project | A buildable unit inside a workspace, defined by a PROJECT file. | Project |
| Phase | An optional workspace-declared ordering boundary that groups targets and can depend on earlier phases. | Phase Block |
| Target | A named goal such as build, test, or dist. | Project Target Block, Workspace Target Block |
| Task | One concrete target execution for one project. | Tasks |
| Workspace | The monorepo root, defined by a WORKSPACE file. | Workspace |
Related Documentation
- Key Concepts - Detailed explanations of core concepts
- Graph - Build graph structure
- Caching - How caching works
- Syntax - Configuration file syntax reference
- Quick Start - Hands-on tutorial