GitHub user brennonyork opened a pull request:
https://github.com/apache/spark/pull/4734
[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!
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/brennonyork/spark SPARK-3355
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/4734.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 #4734
----
commit 3540de917b2cc808711fe9d2e87382d95c2b25e4
Author: Brennon York <[email protected]>
Date: 2015-01-27T21:23:11Z
added an AMPLAB_JENKINS_BUILD_TOOL env. variable to allow differentiation
between maven and sbt build / test suites
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
