A build manifest is a YAML file that describes how to perform a build.
Here's an example:
image: archlinux
packages:
- meson
- scdoc
- wayland-protocols
- wlroots-git
- wayland
- libxkbcommon
- cairo
- pango
- gdk-pixbuf2
- pixman
- libinput
- xorg-server-xwayland
sources:
- https://github.com/swaywm/sway
tasks:
- setup: |
cd sway
meson build
- build: |
cd sway
ninja -C build
The minimum build manifest has an image and at least one task. The various properties available are described here:
string
Which OS image to build in. A list of available build images can be found on the compatibility page.
string
Which architecture to build for. See the compatibility page for a list of available architectures.
list (of string)
A list of packages to install on the image. For image-specific details, consult the compatibility page
dictionary (of string: string)
A list of extra repositories to enable with the image's package manager. The specific format varies by base image, consult the compatibility page for details.
list (of string)
A list of files to extract from the completed build environment and make available for downloading from the jobs page. Artifacts are only uploaded for successful jobs and are pruned after 90 days.
Note that the file names are interpreted literally: do not use ~
or any shell
code. If a relative path is used (e.g. example/my-artifact.tar.gz
), it will be
interpreted relative to the build user's home directory.
boolean
Whether to keep the build VM alive after all of the tasks have finished, even if it doesn't fail, so you can SSH in. You can also SSH in before the tasks have finished and tail the output of the build in your terminal. Learn more about SSH access to build VMs.
list (of string)
A list of repositories to clone into the home directory of the build user in the build environment. Optionally, prefix the protocol with the source control management scheme, to specify a protocol other than git. To specify a non-default git revision, append #commit-object to the repository.
Examples:
https://git.sr.ht/~sircmpwn/scdoc
: git over httpshttps://git.sr.ht/~sircmpwn/scdoc#devel
: git over https (devel branch)git@git.sr.ht:~sircmpwn/scdoc
: git over SSH
(requires key)hg+https://hg.sr.ht/~sircmpwn/scdoc
: Mercurial over httpshg+ssh://hg.sr.ht/~sircmpwn/scdoc
: Mercurial over SSH
(requires key)list (of string)
A list of scripts to execute in the build environment. These scripts are run with the following preamble:
#!/usr/bin/env bash
. ~/.buildenv
set -xe
# Deprecated -- use hut instead
acurl() (
set +x
curl --oauth2-bearer "$OAUTH2_TOKEN" "$@"
)
~/.buildenv contains environment variables specified by the environment
directive.
Task names must use only lowercase alphanumeric characters, underscores or dashes and must be <=128 characters in length. Tasks are executed in the order specified.
Each task is run in a separate login session, so if you modify the groups of the
build
user they will be effective starting from the subsequent task.
list (of trigger)
A list of triggers to execute post-build, which can be used to send emails or do other post-build tasks.
See also: Build triggers
dictionary (of string: string OR string: list)
A list of key/value pairs for options to set in the build environment via
~/.buildenv
.
list (of string)
List of secret UUIDs to be added to the guest during the build. See also: secrets.
string
If present, and secrets are enabled for this build, an OAuth 2.0 bearer token is
generated for this build with the given string as the list of grants. The
hut tool may be used in the task scripts to
perform authenticated GraphQL API requests.
hut needs to be included in the packages
list (using the name
of the hut package for your OS).
commit 3f05846d481ab9c50df85ab9cd5c830f9f695b7c Author: Drew DeVault <sir@cmpwn.com> Date: 2025-01-24T10:44:31+01:00 graphql: document api-meta.json webhook key