[SUBMARINE-388] [k8s-e2e] Rebuild submarine image every run k8s-test

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.4.0
• Component/s: E2E Test
• Labels: pull-request-available
• Target Version: 0.4.0
• Assignee: Liu Xun
• Reporter: Liu Xun
• Created: 15/Feb/20 12:24
• Updated: 26/Jun/20 14:22
• Resolved: 20/Feb/20 12:10

Description

1. 1. k8s test

k8s test: When the user submits the code to his/her repository or the `apache/submarine` git repository, the travis test task will automatically start.

test-k8s runs test cases in travis. It will first create a k8s cluster by using the kind tool in travis,

and then compile and package the submarine project in `submarine-dist` directory to build a docker image.

Then use this latest code build docker image in k8s Deploy a submarine system. Then run test case in the `test-k8s/..` directory.

1. 1. 1. Run k8s test in locally

Executing the following command will perform the following actions:

```
mvn -Phadoop-2.9 clean package install -DskipTests verify -DskipRat -am -pl submarine-test/test-k8s
```

1. The submarine project will be compiled and packaged to generate `submarine-dist/target/submarine-<version>.tar.gz`
2. Call the `submarine-cloud/hack/integration-test.sh` script

+ Call the `build.sh` script under `submarine/dev-support/docker-images/` to generate the latest `submarine`, `database` and `operator` docker images.
+ Call `submarine-cloud/hack/kind-cluster-build.sh` to create a k8s cluster
+ Call `submarine-cloud/hack/deploy-submarine.sh` to deploy the submarine system in the k8s cluster using the latest `submarine`, `database` and `operator` docker images.
+ Call the test cases in `submarine-test/test-k8s/` for testing.

1. 1. 1. Run k8s test in travis

Each time a code is submitted, travis is automatically triggered for testing.

Issue Links

• links to: GitHub Pull Request #185