Concepts
Concepts
Every word bldr uses, in a sentence or two each, with a page on the ones worth more.
The whole vocabulary, briefly. Follow a link when a word starts mattering to you, not before.
| Workspace | A directory with a bldr-workspace.yml. The unit you register with a node and build. |
| Member | One buildable thing inside a workspace: a directory, a git repository, a container image. |
| Target | One thing a member can produce. Your build code declares them; a build picks among them. |
| Build | One run of your build code against a workspace, producing the targets you asked for. |
| Artifact | Content addressed by the hash of its bytes. What every target produces and every step consumes. |
| Pod | A container bldr runs a build step in. Content goes in, content comes out. |
| Cache | Why a build that has nothing new to do does nothing. |
| Run | Something kept running, backed by a build. |
| Deployment | A declared step you invoke against what a build produced. |
| Node | The daemon that stores content and runs pods. Your machine talks to one; it does the work. |
| Function | A named, versioned operation a node knows how to perform, such as pod.dag/v0.0.0. Build code calls them; you rarely name one directly. |
| Ref | A name pointing at content, so you can say release instead of a hash. |
The shape of it
Five words carry most of the weight, and they nest:
workspace the directory you build
└── member one buildable thing in it
└── target one thing that member produces
↑
a build selects targets and produces artifacts
↓
a run or a deployment acts on what came outEverything else is detail underneath that.