cage/.travis.yml

language: c
os: linux

services:
  - docker

before_install:
  # Add the automatically checked out repository to the Docker image.
  - echo "ADD . /root/cage" >> Dockerfile
  # Build the Docker image.
  - docker build -t hjdskes/cage .

script:
  # Build Cage with AddressSanitizer (incl. LeakSanitizer) and
  # UndefinedBehaviorSanitizer, which will be instrumented during execution.
  # TODO: find a nicer way to kill termite in order to get Cage to exit.
  - docker run hjdskes/cage /bin/bash -c "export CC=gcc && meson build -Db_sanitize=address,undefined && ninja -C build && (sleep 5 && pkill -9 termite) & xvfb-run ./build/cage termite"

  # Build Cage with MemorySanitizer, which will also instrument Cage during
  # execution. Since we can't use all sanitizers together, we have to duplicate
  # this process here. TODO: This does not work with GCC.
  # - docker run hjdskes/cage /bin/bash -c "export CC=gcc && meson build -Db_sanitize=memory && ninja -C build && (sleep 5 && pkill -9 termite) & xvfb-run ./build/cage termite"

after_script:
  # If Cage ran successfully and without any memory errors or undefined behavior
  # (in those parts exercised by launching a client and exiting almost
  # immediately), we run Clang's Static Analyzer on Cage.
  - docker run hjdskes/cage /bin/bash -c "export CC=clang && meson build && ninja -C build scan-build"
Add a Travis CI build This isn't an optimal build: 1. We're using an untagged, rolling Arch Linux base image for our Docker image, meaning that potentially every build uses a different base. The reason for using an Arch base is because Arch is the only system that has new enough versions of wlroots' dependencies. Alpine has this too, but is sufficiently different (e.g. musl and no logind) from other systems such that I'm not sure whether it will be of any benefit. In the future, when wlroots is less bleeding edge, we can switch to tagged releases of e.g. Fedora. 2. We don't have access to hardware, hence we cannot run with wlroots' headless backend. We can solve this by making the hardware available to our container with docker's --device=/dev/dri/renderD128, but we don't have control over this inside our Travis instance. Hence, we need to run with wlroots' x11 backend through xvfb. Still, it's better than nothing and we will at least get to know whether Cage builds and can start up, open a window and close. For good measure, I also threw in Clang's analyses so we'll learn about potential issues here as well. 2019-02-21 14:50:05 +01:00			`language: c`
			`os: linux`

			`services:`
			`- docker`

			`before_install:`
			`# Add the automatically checked out repository to the Docker image.`
			`- echo "ADD . /root/cage" >> Dockerfile`
			`# Build the Docker image.`
			`- docker build -t hjdskes/cage .`

			`script:`
			`# Build Cage with AddressSanitizer (incl. LeakSanitizer) and`
			`# UndefinedBehaviorSanitizer, which will be instrumented during execution.`
			`# TODO: find a nicer way to kill termite in order to get Cage to exit.`
			`- docker run hjdskes/cage /bin/bash -c "export CC=gcc && meson build -Db_sanitize=address,undefined && ninja -C build && (sleep 5 && pkill -9 termite) & xvfb-run ./build/cage termite"`

			`# Build Cage with MemorySanitizer, which will also instrument Cage during`
			`# execution. Since we can't use all sanitizers together, we have to duplicate`
			`# this process here. TODO: This does not work with GCC.`
			`# - docker run hjdskes/cage /bin/bash -c "export CC=gcc && meson build -Db_sanitize=memory && ninja -C build && (sleep 5 && pkill -9 termite) & xvfb-run ./build/cage termite"`

			`after_script:`
			`# If Cage ran successfully and without any memory errors or undefined behavior`
			`# (in those parts exercised by launching a client and exiting almost`
			`# immediately), we run Clang's Static Analyzer on Cage.`
			`- docker run hjdskes/cage /bin/bash -c "export CC=clang && meson build && ninja -C build scan-build"`