Don't execute compose/blueprint sanity tests in Travis CI

instead they will be executed in Cockpit CI
This commit is contained in:
Alexander Todorov 2019-05-27 16:30:44 +03:00 committed by Lars Karlitski
parent c5ae344b4f
commit 6c2b34bf15
2 changed files with 3 additions and 3 deletions

View File

@ -52,8 +52,6 @@ test:
coverage3 report -m coverage3 report -m
[ -f "/usr/bin/coveralls" ] && [ -n "$(COVERALLS_REPO_TOKEN)" ] && coveralls || echo [ -f "/usr/bin/coveralls" ] && [ -n "$(COVERALLS_REPO_TOKEN)" ] && coveralls || echo
./tests/test_cli.sh
# need `losetup`, which needs Docker to be in privileged mode (--privileged) # need `losetup`, which needs Docker to be in privileged mode (--privileged)
# but even so fails in Travis CI # but even so fails in Travis CI
test_images: test_images:

View File

@ -5,6 +5,8 @@ we're checking out Cockpit's `bots/` subdirectory. It contains links to test
images and tools to manipulate and start virtual machines from them. images and tools to manipulate and start virtual machines from them.
Each test is run on a new instance of a virtual machine. Each test is run on a new instance of a virtual machine.
Branch/test matrix is configured in `bots/tests-scan` inside the
[cockpit repository](https://github.com/cockpit-project/cockpit).
## Dependencies ## Dependencies