GitHub user Remilito opened a pull request:
https://github.com/apache/zeppelin/pull/2167
[ZEPPELIN-2230] .travis.yml protecting against ambiguous commit range
### What is this PR for?
Following the revert of [](https://github.com/apache/zeppelin/pull/2111
) I added some protection in case TRAVIS_COMMIT_RANGE is "ambiguous" i.e.
some paths or commits are not found within the range. (can happen on some push
--force).
### What type of PR is it?
Bug Fix
### Todos
* [ ] - Task
### What is the Jira issue?
[ZEPPELIN-2230](https://issues.apache.org/jira/browse/ZEPPELIN-2230)
### How should this be tested?
Re-do a twisted git push --force.
### 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/Remilito/zeppelin ZEPPELIN-2230b
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2167.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 #2167
----
commit cb9647f10dc2879ec6a2e0ae338067bd1e919958
Author: Remilito <remy.ga...@gmail.com>
Date: 2017-03-07T17:32:12Z
[ZEPPELIN-2230] clear bower_contents if bower.json changed or bower
clear provided in commit message
commit 97968f915b27dfe51163c1181aa8a13c87f560d1
Author: Remilito <remy.ga...@gmail.com>
Date: 2017-03-20T10:32:59Z
Protecting against ambiguous TRAVIS_COMMIT_RANGE.
E.g.: when push force, some commits might be missing from the origin
branch, therefore causing an unsusable COMMIT_RANGE.
----
---
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.
---
