Home

Tamp Wiki

Pack the build down tight.

A small-core, plugin-driven build automation framework for .NET. Cross-platform. Honest about resources. Forkable.

This wiki is the developer-facing reference. The main README carries the elevator pitch and the project's design philosophy; everything operational lives here.

Start here

• Getting Started — install the global tool, scaffold a Build.cs, run your first target. 5 minutes.
• Build Script Authoring — the fluent target DSL, dependencies, conditionals, failure handlers.
• Parameter & Secret Injection — [Parameter], [Secret], value-injection attributes ([Solution], [GitRepository], [NuGetPackage]).

Modules

• Module Catalog — overview of the Tamp.* package family + version-pin convention.
  • In the tamp repo: Tamp.NetCli.V8 / V9 / V10 — dotnet SDK CLI wrapper.
  • Containers / build: Tamp.Docker.V27 (incl. compose + buildx).
  • JS toolchain: Tamp.Yarn.V4, Tamp.Turbo.V2, Tamp.Vite.V5 (Vite + Vitest), Tamp.GraphQLCodegen.V5.
  • Testing: Tamp.Playwright.V1 — sharded e2e.
  • Security scanning: Tamp.TruffleHog.V3, Tamp.CodeQL.V2.

Tooling primitives

• AbsolutePath, RootDirectory, TemporaryDirectory — first-class path type with / operator, glob, hash, copy/move; build-script statics.
• Verify — runtime preconditions for build scripts.

Execution and observability

• Logging & Verbosity — LogLevel, --verbosity, build summary table.
• Failure Handling — FailureMode, OnFailureOf, AssuredAfterFailure, OnlyWhen vs Requires.

CI integration

• CI Host Integrations — typed adapters and emit commands for GitHub Actions, Azure DevOps, TeamCity.

Migration

• Migrating from NUKE — concept-by-concept mapping. Where Tamp matches NUKE's surface and where it deliberately diverges.
• Migrating from Cake — Cake script + addins → Tamp Build.cs + modules.

Reference

• FAQ
• Glossary
• Architecture Decision Records — every load-bearing design choice is recorded under docs/adr/ in the main repo. Read these before proposing a change to the corresponding area.

Project meta

• Repository — source, issues, releases.
• Changelog — release notes.
• Maintainers — who's authorised on this project.
• Code of Conduct.
• Security policy — vulnerability disclosure.