Fix Travis IPv6 and add k8s integration testing to CI (#194)

Updating travis yaml file to:
* Force IPv6 to work in their VM environment
* Enable docker (requires VM environment and sudo)
* Run kubernetes integration tests in Travis
This commit is contained in:
Michael Richmond
2016-07-27 10:01:24 -07:00
committed by GitHub
parent 4a3b57d81b
commit 8dec292668
8 changed files with 54 additions and 13 deletions

View File

@@ -102,7 +102,7 @@ kubectl to communicate with kubernetes running on the localhost:
~~~
#!/bin/bash
BASEDIR=`realpath $(dirname ${0})`
BASEDIR=`readlink -e $(dirname ${0})`
${BASEDIR}/kubectl config set-cluster test-doc --server=http://localhost:8080
${BASEDIR}/kubectl config set-context test-doc --cluster=test-doc
@@ -343,12 +343,14 @@ TBD:
* Do we need to generate synthetic zone records for namespaces?
* Do we need to generate synthetic zone records for the skydns synthetic zones?
* Test cases
* ~~Implement test cases for http data parsing using dependency injection
for http get operations.~~
* Test with CoreDNS caching. CoreDNS caching for DNS response is working
using the `cache` directive. Tested working using 20s cache timeout
and A-record queries. Automate testing with cache in place.
* Automate CoreDNS performance tests. Initially for zone files, and for
pre-loaded k8s API cache.
* Automate integration testing with kubernetes. (k8s launch and service start-up
automation is in middleware/kubernetes/tests)
* Try to get rid of kubernetes launch scripts by moving operations into
.travis.yml file.
* ~~Implement test cases for http data parsing using dependency injection
for http get operations.~~
* ~~Automate integration testing with kubernetes. (k8s launch and service start-up
automation is in middleware/kubernetes/tests)~~