Guide to Dynamic Builds

📄️ Key Concepts

BuildBeaver is centered on the idea of fully dynamic builds that can be run anywhere. That means on your laptop,

Workflows are groups of jobs. Each workflow can be run separately but can have dependencies on other workflows.

A workflow handler function is responsible for submitting Jobs to be run as part of the build. Each job

Steps are individually tracked units of work within a job; the BuildBeaver server can show the progress within a

Jobs can run either in a Docker container ('docker' jobs) or natively on the machine where the runner or bb

To fully take advantage Dynamic Builds the Build Controller program will often need to run code after another

One of the powerful features of the BuildBeaver SDK is the ability for code to read the current status of the build,

Fingerprints allow the running of a Job to be skipped if the Artifacts from a previously successful run

Services are processes that can be run alongside a Job to provide supporting capabilities while the Job runs.

The following Go code is a real-world Build Controller, and demonstrates many of the dynamic features of the