GitHub user vanzin opened a pull request: https://github.com/apache/spark/pull/22909
[SPARK-25897][k8s] Hook up k8s integration tests to sbt build. The integration tests can now be run in sbt if the right profile is enabled, using the "test" task under the respective project. This avoids having to fall back to maven to run the tests, which invalidates all your compiled stuff when you go back to sbt, making development way slower than it should. There's also a task to run the tests directly without refreshing the docker images, which is helpful if you just made a change to the submission code which should not affect the code in the images. The sbt tasks currently are not very customizable; there's some very minor things you can set in the sbt shell itself, but otherwise it's hardcoded to run on minikube. I also had to make some slight adjustments to the IT code itself, mostly to remove assumptions about the existing harness. Tested on sbt and maven. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vanzin/spark SPARK-25897 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/spark/pull/22909.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #22909 ---- commit 0d8c7f6d883818cbdd2b830d1829b505e8263e2a Author: Marcelo Vanzin <vanzin@...> Date: 2018-10-30T18:18:16Z [SPARK-25897][k8s] Hook up k8s integration tests to sbt build. The integration tests can now be run in sbt if the right profile is enabled, using the "test" task under the respective project. This avoids having to fall back to maven to run the tests, which invalidates all your compiled stuff when you go back to sbt, making development way slower than it should. There's also a task to run the tests directly without refreshing the docker images, which is helpful if you just made a change to the submission code which should not affect the code in the images. The sbt tasks currently are not very customizable; there's some very minor things you can set in the sbt shell itself, but otherwise it's hardcoded to run on minikube. I also had to make some slight adjustments to the IT code itself, mostly to remove assumptions about the existing harness. Tested on sbt and maven. ---- --- --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org