ostree/.travis.yml

language: c
dist: trusty
sudo: required

env:
  - ci_distro=ubuntu ci_suite=trusty ci_test=no  # TODO: use libcurl on this
  - ci_docker=debian:jessie-slim ci_distro=debian ci_suite=jessie
  - ci_docker=debian:jessie-slim ci_distro=debian ci_suite=jessie ci_configopts="--with-curl"
  - ci_docker=debian:stretch-slim ci_distro=debian ci_suite=stretch ci_test=no  # TODO gpgme flake https://github.com/ostreedev/ostree/pull/664#issuecomment-276033383
  - ci_docker=ubuntu:xenial ci_distro=ubuntu ci_suite=xenial

script:
  - ci/travis-install.sh
  - ci_parallel=2 ci_sudo=yes ci/travis-build.sh

notifications:
  email: false
travis: run the test suite on various distributions .travis.yml is obviously still Travis-specific, but tests/ci-* are designed to be shareable with other CI environments if there is interest in doing so. At the moment I'm only testing on Debian and Ubuntu. In principle we could try a non-Debian-derived Docker container such as Fedora or CentOS inside travis-ci's Ubuntu environment, similar to what I'm doing for Debian, but I don't know the correct setup commands to use there. Closes: #438 Approved by: cgwalters 2016-08-06 00:12:55 +03:00			`language: c`
			`dist: trusty`
			`sudo: required`

			`env:`
travis: Disable tests (but keep builds) on flaky distros I went through the Travis history a bit, and these seem to be the flaky ones. The ubuntu one is likely no libsoup patches. The other one @smcv has partially traced to a GPGME race condition or something like that. For the libsoup one; as I say in comments, once we have libcurl, I'd like to enable that mostly everywhere, which should (hopefully) be more reliable. Closes: #664 Approved by: cgwalters 2017-01-30 13:21:43 +03:00			`- ci_distro=ubuntu ci_suite=trusty ci_test=no # TODO: use libcurl on this`
travis-ci: Use "slim" Debian image for testing Documentation and similar files are stripped from this image, making it quicker to install. Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Closes: #600 Approved by: cgwalters 2016-11-28 20:24:55 +03:00			`- ci_docker=debian:jessie-slim ci_distro=debian ci_suite=jessie`
libcurl backend For rpm-ostree, we already link to libcurl indirectly via librepo, and only having one HTTP library in process makes sense. Further, libcurl is (I think) more popular in the embedded space. It also supports HTTP/2.0 today, which is a very nice to have for OSTree. This seems to be working fairly well for me in my local testing, but it's obviously brand new nontrivial code, so it's going to need some soak time. The ugliest part of this is having to vendor in the soup-url code. With Oxidation we could follow the path of Firefox and use the [Servo URL parser](https://github.com/servo/rust-url). Having to redo cookie parsing also sucked, and that would also be a good oxidation target. But that's for the future. Closes: #641 Approved by: jlebon 2016-12-08 05:02:30 +03:00			`- ci_docker=debian:jessie-slim ci_distro=debian ci_suite=jessie ci_configopts="--with-curl"`
travis: Disable tests (but keep builds) on flaky distros I went through the Travis history a bit, and these seem to be the flaky ones. The ubuntu one is likely no libsoup patches. The other one @smcv has partially traced to a GPGME race condition or something like that. For the libsoup one; as I say in comments, once we have libcurl, I'd like to enable that mostly everywhere, which should (hopefully) be more reliable. Closes: #664 Approved by: cgwalters 2017-01-30 13:21:43 +03:00			`- ci_docker=debian:stretch-slim ci_distro=debian ci_suite=stretch ci_test=no # TODO gpgme flake https://github.com/ostreedev/ostree/pull/664#issuecomment-276033383`
travis: run the test suite on various distributions .travis.yml is obviously still Travis-specific, but tests/ci-* are designed to be shareable with other CI environments if there is interest in doing so. At the moment I'm only testing on Debian and Ubuntu. In principle we could try a non-Debian-derived Docker container such as Fedora or CentOS inside travis-ci's Ubuntu environment, similar to what I'm doing for Debian, but I don't know the correct setup commands to use there. Closes: #438 Approved by: cgwalters 2016-08-06 00:12:55 +03:00			`- ci_docker=ubuntu:xenial ci_distro=ubuntu ci_suite=xenial`

			`script:`
ci: Move travis scripts from tests/ → ci/ I think tests/ should be just that, ci/ is separate. Also rename the files to include "travis" since that's what we use them for right now. Closes: #843 Approved by: jlebon 2017-05-09 18:52:20 +03:00			`- ci/travis-install.sh`
			`- ci_parallel=2 ci_sudo=yes ci/travis-build.sh`
travis: Disable email notifications I'm getting spammed. We'll see the results in the status. Closes: #450 Approved by: jlebon 2016-08-09 19:51:30 +03:00
			`notifications:`
			`email: false`