Github user vistep commented on the issue:
https://github.com/apache/zeppelin/pull/2521
@Leemoonsoo How about the idea above?
---
Github user vistep commented on the issue:
https://github.com/apache/zeppelin/pull/2521
Can we use a try-catch block to test if we need to set working directory
when zeppelin opens a shell interpreter?
---
Github user vistep commented on the issue:
https://github.com/apache/zeppelin/pull/2521
I tried again and it passed.
---
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
Github user vistep commented on the issue:
https://github.com/apache/zeppelin/pull/2521
I replaced System.getenv("HOME") with System.getProperty("user.home") .
This time, Jenkins said "[ERROR] Failed to execute goal
com.github.eirslett:frontend-maven-p
Github user vistep commented on the issue:
https://github.com/apache/zeppelin/pull/2521
I have fix the build problem by setting travis according to what Jenkins
said at last part.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user vistep commented on the issue:
https://github.com/apache/zeppelin/pull/2521
Jenkins said that "Can't find build for commit
e8cbdd180a22d1d53366c94c5432c217d70a5727 from vistep".
I have no idea about what happened. How to fix it?
---
If your project
