Skip to content

Environments on demand

A job’s execution environment is prepared for each run and thrown away when the run ends. It is not a standing environment that everyone shares.

How environments are prepared

  • When a run is set, Zuul’s launcher prepares the environment. The main route is a Kubernetes Pod
  • The kind of environment is chosen by the name of the kind (a “label”). One name corresponds to a set: an image, which decides the operating system and tools, and a size of CPU and memory
  • When the running side specifies the name, the launcher builds the matching environment (a Pod or a VM). The side specifying it does not need to know how it is built
  • When the job ends, the environment is discarded

What this means for you

  • Every run starts from a clean state. Nothing left over from a previous run leaks into the result
  • You do not have to think about the providing side’s concerns, such as free standing machines or cleanup
  • Environments exist only when needed, in the amount needed, so unused ones do not linger

The e2e test environments are prepared on this same mechanism.