selinux/scripts/ci
William Roberts 1af345d222 ci: dont use hardcoded project name
Not everyone's github project is "selinux" so use the projects
name, as derived from TRAVIS_BUILD_DIR. TRAVIS_BUILD_DIR is
the absolute path to the project checkout on disk, so the
basename should be sufficient. The script that runs in the KVM
environment also needs to be updated where it can find the
selinux project code, so we pass it in through an env variable
in the ssh command.

Tested on Travis CI here:
  - https://travis-ci.org/github/williamcroberts/selinux/jobs/697307824

Signed-off-by: William Roberts <william.c.roberts@intel.com>
Acked-by: Petr Lautrbach <plautrba@redhat.com>
2020-06-18 19:22:37 +02:00
..
README.md ci: run SELinux kernel test suite 2020-06-18 19:22:12 +02:00
fedora-test-runner.sh ci: dont use hardcoded project name 2020-06-18 19:22:37 +02:00
travis-kvm-setup.sh ci: dont use hardcoded project name 2020-06-18 19:22:37 +02:00

README.md

Continuous Integration Scripts

The scripts under scripts/ci are designed specifically for the Travis CI system. While nothing prevents you from mimicking that environment and using them locally, they are not applicable for general consumption. Any thing in this directory should never be considered as a stable API.