Suricata Test Build Environments - Using Docker and Vagrant
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
docker-centos-6
docker-centos-7
docker-debian-8
docker-debian-9
docker-fedora-28
docker-ubuntu-1404
docker-ubuntu-1604
vagrant-freebsd-11.1-stable
vagrant-openbsd-6.2
.gitignore
README.md
builds.yaml
run.py

README.md

Test Builders for Suricata

A set of Docker and Vagrant images for testing builds of Suricata.

Usage

From your Suricata build directory:

/path/to/suricata-test-builders/run.py

Examples

Run all builds

/path/to/suricata-test-builders/run.py

Just run the centos-7-basic build:

/path/to/suricata-test-builders/run.py centos-7-basic

Just run builds with the ubuntu or debian labels:

/path/to/suricata-test-builders/run.py ubuntu debian

Just run builds with the "rust" and "distcheck" labels:

/path/to/suricata-test-builders/run.py rust+distcheck

Skip builds with the "cocci" label:

/path/to/suricata-test-builders/run.py --skip cocci

Get a shell in a specific build

/path/to/suricata-test-builders/run.py --shell vagrant-freebsd-11.1-stable

libhtp

The libhtp used in the build will be determined by what is found first:

  • the libhtp directory in the Suricata source tree (bundled).
  • the directory pointed to by the LIBHTP_DIR environment variable.
  • if neither of the above, libhtp will be cloned and cached

The environment variables LIBHTP_REPO and LIBHTP_BRANCH can be used to override the branch and repo that libhtp is cloned from.