Installation

E2Engine can be run directly as a command-line application or as a container image. Install the e2engine CLI for local use, or use the E2Engine image in CI/CD and other containerized environments.

Choose how to run E2Engine

For local development, the simplest option is to install and run the e2engine CLI directly.

For CI/CD pipelines and other containerized environments, E2Engine can be run as a container image instead. Docker is not required to use the CLI itself.

Install the CLI locally

macOS

Install E2Engine using Homebrew:

brew install --cask e2engine/tap/e2engine

Linux

Download the appropriate .deb or .rpm package for your architecture from the latest GitHub release.

Debian/Ubuntu:

sudo apt install ./e2engine_*.deb

Fedora/RHEL:

sudo dnf install ./e2engine_*.rpm

Windows

Install E2Engine using Scoop:

scoop bucket add e2engine https://github.com/e2engine/scoop-bucket
scoop install e2engine

Download a release

Prebuilt binaries are available from the E2Engine CLI GitHub releases page.

Download the archive for your platform, extract the e2engine binary, and place it somewhere on your PATH.

Build from source

If you have Go installed, you can build the CLI directly from the repository:

git clone https://github.com/e2engine/cli.git
cd cli
go build -o e2engine .

Move the resulting binary somewhere on your PATH if you want to invoke it globally.

Verify the installation

Run:

e2engine version

If the command prints the installed E2Engine version, the CLI is ready to use.

You can also inspect the available commands with:

e2engine --help

CI/CD and containerized environments

For automated pipelines, E2Engine can be run as a container image instead of installing the CLI on the runner.

See CI/CD pipelines for guidance on running E2Engine in CI/CD environments.

Next step

With the CLI ready, continue to Your first test to define an environment and execute an E2Engine test.