GitHub user Leemoonsoo opened a pull request:
https://github.com/apache/zeppelin/pull/2342
[ZEPPELIN-2467] Restore travis second job functionality
### What is this PR for?
issue ZEPPELIN-2467 has resolved by
https://github.com/apache/zeppelin/pull/2300. However
https://github.com/apache/zeppelin/commit/8194a5e0af0e1b926b27ea9e0d12bdf9d0e43b4b
reverts #2300.
This PR apply #2300 again with two more test exclusion:
- SecurityRestApiTest
(https://issues.apache.org/jira/browse/ZEPPELIN-2545)
- NotebookSecurityRestApiTest
(https://issues.apache.org/jira/browse/ZEPPELIN-2546)
### What type of PR is it?
Bug Fix
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-2467
### How should this be tested?
CI becomes green
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Leemoonsoo/zeppelin fix_ci2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2342.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 #2342
----
commit 41af70f4f039ddec8323fc1b3da023aa7069420d
Author: Alexander Shoshin <[email protected]>
Date: 2017-04-28T13:18:15Z
added ability to exclude some unit tests using command line
commit 95eb7be863af83e943313a3daeb6bfd4c1d83b5c
Author: Alexander Shoshin <[email protected]>
Date: 2017-04-28T13:22:08Z
changed -Dtest flag to -Dtests.to.exclude and excluded unstable tests
commit 4f822432e897da07b8ece90178a6153b72ff0aac
Author: Alexander Shoshin <[email protected]>
Date: 2017-05-03T08:45:15Z
made a comment about excluded tests
commit 1a8f24be326239e4c7746c7b7f3e372ca21845aa
Author: Lee moon soo <[email protected]>
Date: 2017-05-14T22:05:41Z
exclude SecurityRestApiTest and NotebookSecurityRestApiTest
----
---
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.
---
