:
Just a quick note to everyone that Patrick and I are playing around with
Travis CI on the Spark github repository. For now, travis does not run all
of the test cases, so will only be turned on experimentally. Long term it
looks like Travis might give better integration with github, so we
Is the migration from Jenkins to Travis finished?
It is not finished and really at this point it is only something we are
considering, not something that will happen for sure. We turned it on in
addition to Jenkins so that we could start finding issues exactly like the
ones you described
Just a quick note to everyone that Patrick and I are playing around with
Travis CI on the Spark github repository. For now, travis does not run all
of the test cases, so will only be turned on experimentally. Long term it
looks like Travis might give better integration with github, so we
I assume the Jenkins is not working now?
Best,
--
Nan Zhu
On Tuesday, March 25, 2014 at 6:42 PM, Michael Armbrust wrote:
Just a quick note to everyone that Patrick and I are playing around with
Travis CI on the Spark github repository. For now, travis does not run all
of the test cases
:
Just a quick note to everyone that Patrick and I are playing around with
Travis CI on the Spark github repository. For now, travis does not run all
of the test cases, so will only be turned on experimentally. Long term it
looks like Travis might give better integration with github, so we
at 6:42 PM, Michael Armbrust wrote:
Just a quick note to everyone that Patrick and I are playing around with
Travis CI on the Spark github repository. For now, travis does not run all
of the test cases, so will only be turned on experimentally. Long term it
looks like Travis might give
note to everyone that Patrick and I are playing around with
Travis CI on the Spark github repository. For now, travis does not run all
of the test cases, so will only be turned on experimentally. Long term it
looks like Travis might give better integration with github, so we are
going to see
