GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/2102
[Hot Fix] Remove 'bower_component' from caching list in travis cfg file
### What is this PR for?
After #2042 merged, cached `bower_components/` causes CI failure like
```
"message": "Unable to find suitable version for d3" (bower installation
failure)
```
```
[ERROR] [{
[ERROR] "code": "ECONFLICT",
[ERROR] "name": "d3",
[ERROR] "picks": [
[ERROR] {
[ERROR] "endpoint": {
[ERROR] "name": "d3",
[ERROR] "source": "d3",
[ERROR] "target": "~3.3.13"
[ERROR] },
[ERROR] "canonicalDir":
"/home/travis/build/apache/zeppelin/zeppelin-web/bower_components/d3",
[ERROR] "pkgMeta": {
[ERROR] "name": "d3",
[ERROR] "version": "3.3.13",
[ERROR] "main": "d3.js",
[ERROR] "scripts": [
[ERROR] "d3.js"
[ERROR] ],
...
```
It can be resolved in each contributors' travis account by deleting all
cache in their repository like
[this](https://github.com/apache/zeppelin/pull/2042#issuecomment-284324008),
but current Zeppelin master is under Apache travis account. So we need to clear
the cache by removing `zeppelin-web/bower_components` in caching list in
`.travis.yml`.
Let's see the master branch's CI turns to green light :)
### What type of PR is it?
Hot Fix
### What is the Jira issue?
No Jira issue for this
### How should this be tested?
No need to test
### Screenshots (if appropriate)
### 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/AhyoungRyu/zeppelin makeCIHappy
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2102.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 #2102
----
commit 05c802c4ab51a6292616c8369afa9cb8cd05d72b
Author: AhyoungRyu <fbdkdu...@hanmail.net>
Date: 2017-03-07T02:58:15Z
Remove 'bower_component' from caching list in travis cfg file
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
