batect can be run on any Buildkite agent that meets batect's system requirements - chiefly Docker and a JVM.
Running with command evaluation disabled¶
Buildkite supports disabling command evaluation, which requires all build scripts to be invoked without arguments and take any necessary input as environment variables. This prevents the use of the batect wrapper script, as it expects to receive the task name and other options as command line options.
There are two solutions to this:
Option 1: create step-specific shell scripts that invoke batect¶
In this scenario, you create multiple shell scripts, one for each step in Buildkite.
For example, let's say you have three steps in Buildkite: one for building, one for testing, and another for packaging. You would need to create a separate script for each of these steps that invokes batect.
Each script would be similar to the following example script that runs a series of different kinds of tests:
#! /usr/bin/env bash set -euo pipefail ./batect unitTest ./batect integrationTest ./batect journeyTest
Option 2: create a wrapper script that takes the task name as an environment variable¶
In this scenario, you create a single shell script and invoke it with different environment variable values for each step.
A basic wrapper script could look something like this:
#! /usr/bin/env bash set -euo pipefail ./batect "$BATECT_TASK"
Configure this in your Buildkite
pipeline.yml as follows:
steps: - label: Run build command: scripts/batect-wrapper.sh env: BATECT_TASK: build - label: Run unit tests command: scripts/batect-wrapper.sh env: BATECT_TASK: unitTest # ...and so on