THE AUTOMATION TOOL

Nexus Forge

The build is part of the workflow.

Nexus Forge executes declarative automation written in Nexus Script. Compose project builds with filesystem operations, downloads, archive extraction, Git checkouts, rendering, and release assembly.

Compose existing operations

Groups, projects, and packages execute their children in declaration order and stop on failure. Recipes can express shared data and selected platform variants with the same language used elsewhere in Nexus.

Let each tool own its work

Use Nexus Build to build a project. Use Nexus Forge to compose that build with other work. Its NXBuild operation uses the Nexus Build engine rather than maintaining a second build implementation.

Keep automation readable

Explicit operations describe what a workflow does and the data each operation consumes. Use the operation reference to choose the existing capability that fits the task.

Nexus Forge documentation Operation reference

See the source-build guide for how the Nexus repositories use these tools.

Across the ecosystem

Nexus uses Forge recipes to construct its tools and Nexus Gear engine, assemble resources, and prepare outputs. Nexus Code supplies the Pascal and Nexus Script workspace, while Forge owns the wider automation.