aboutsummaryrefslogtreecommitdiff
path: root/sql/core
diff options
context:
space:
mode:
authorBrennon York <brennon.york@capitalone.com>2015-03-04 11:02:33 +0000
committerSean Owen <sowen@cloudera.com>2015-03-04 11:02:33 +0000
commit418f38d92f000b3f62fd363fbbc7ee22583d8ec3 (patch)
treea6cf71c2c8a283593aceb546de42409c9acb93f4 /sql/core
parent8d3e2414d430e1a0eb209eacba2cf739f3eab0c5 (diff)
downloadspark-418f38d92f000b3f62fd363fbbc7ee22583d8ec3.tar.gz
spark-418f38d92f000b3f62fd363fbbc7ee22583d8ec3.tar.bz2
spark-418f38d92f000b3f62fd363fbbc7ee22583d8ec3.zip
[SPARK-3355][Core]: Allow running maven tests in run-tests
Added an AMPLAB_JENKINS_BUILD_TOOL env. variable to allow differentiation between maven and sbt build / test suites. The only issue I found with this is that, when running maven builds I wasn't able to get individual package tests running without running a `mvn install` first. Not sure what Jenkins is doing wrt its env., but figured its much better to just test everything than install packages in the "~/.m2/" directory and only test individual items, esp. if this is predominantly for the Jenkins build. Thoughts / comments would be great! Author: Brennon York <brennon.york@capitalone.com> Closes #4734 from brennonyork/SPARK-3355 and squashes the following commits: c813d32 [Brennon York] changed mvn call from 'clean compile 616ce30 [Brennon York] fixed merge conflicts 3540de9 [Brennon York] added an AMPLAB_JENKINS_BUILD_TOOL env. variable to allow differentiation between maven and sbt build / test suites
Diffstat (limited to 'sql/core')
0 files changed, 0 insertions, 0 deletions