[ 
https://issues.apache.org/jira/browse/SUBMARINE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Liu Xun updated SUBMARINE-388:
------------------------------
    Description: 
## 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.

### 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.

### Run k8s test in travis

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

  was:
The k8s-e2e travis test needs to use the latest compiled package.
Do a docker build so that you can test the latest code.

Now we are using the image we have released on the apache docker hub, so we 
can't test the latest code.


> [k8s-e2e] Rebuild image every run k8s-test
> ------------------------------------------
>
>                 Key: SUBMARINE-388
>                 URL: https://issues.apache.org/jira/browse/SUBMARINE-388
>             Project: Apache Submarine
>          Issue Type: Sub-task
>          Components: E2E Test
>            Reporter: Liu Xun
>            Assignee: Liu Xun
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> ## 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.
> ### 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.
> ### Run k8s test in travis
> Each time a code is submitted, travis is automatically triggered for testing.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to