FatalLin opened a new pull request #615: URL: https://github.com/apache/submarine/pull/615
### What is this PR for? Just like I mentioned in Jira story, it's common for operator members to fix the code of submarine-server when they hit some unexpected error in testing. Our current building tool compiles the whole project each time even they are only made some minor change, it really takes time and slow down the progress. I made a handy script aim to improve the developing progress in these kind of cases. IMPORTANT: The developers have to make a whole project compiling once before using this script. After we execute the script, it will enter the submarine-server directory and start to build the submarine-server module. The second step is moviong to submarin-dist directory to build the assembly tar ball, and call the build script to build image in step three. In the end, the script delete the submarine-server deployment in assigned namespace, and we expect the operator will launch another submarine-server deployment with the latest image. ### What type of PR is it? Improvement ### Todos ### What is the Jira issue? https://issues.apache.org/jira/browse/SUBMARINE-855 ### How should this be tested? usage: `./submarine-cloud-v2/hack/server-rapid-builder.sh <assigned-namespace>` example: ` ./submarine-cloud-v2/hack/server-rapid-builder.sh submarine-user-test` ### Screenshots (if appropriate) <img width="900" alt="ζͺε 2021-06-28 δΈε11 08 56" src="https://user-images.githubusercontent.com/5687317/123664932-63f3ff00-d86a-11eb-8b48-c1efaf7d2064.png"> ### Questions: * Do the license files need updating? Yes/No * Are there breaking changes for older versions? Yes/No * Does this need new documentation? Yes/No -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
