Github user dlukyanov commented on the issue:
https://github.com/apache/zeppelin/pull/2068
Closing this pull request because fork under organization can't be checked
by jenkins job for now (or smth wrong with my hands))
Created new fork [#2135]
And new pull request [https:
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2068
Could you try rebase or merge master to this PR, so this PR branch includes
update on `travis_check.py` that #2094 made?
---
If your project is set up for it, you can reply to this email and h
Github user dlukyanov commented on the issue:
https://github.com/apache/zeppelin/pull/2068
@Leemoonsoo I see that #2094 is closed but I still have a problem with build
Should I move from org to user?
```
++ awk '{print $3}'
++ git log -n 1
++ grep '^Merge:'
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2068
I've made a patch #2094 to make jenkins check repository under
organization. Once #2094 is merged, then Jenkins will able to check this PR
build status correctly.
---
If your project is set u
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2068
hmm, I don't know about organization @Leemoonsoo
as for log, travis was having problems yesterday, perhaps you can try again?
---
If your project is set up for it, you can reply to this e
Github user dlukyanov commented on the issue:
https://github.com/apache/zeppelin/pull/2068
@felixcheung ,
it seems that jenkins job looking for travis build under the author, but i
made branch under organization... are there any restrictions about
author/organization?
and ano
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2068
Please see
https://zeppelin.apache.org/contribution/contributions.html#continuous-integration
for setting up CI.
---
If your project is set up for it, you can reply to this email and have yo
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2068
And I think the other interpreter's PR can be helpful to you (e.g. A PR for
BigQuery Interpreter: #1170 ). Especially [this
comment](https://github.com/apache/zeppelin/pull/1170#issuecomment-23
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2068
@dlukyanov Is this WIP or ready for review? If it's WIP, then could you
update the title to sth like "[WIP][ZEPPELIN-2196] Groovy interpreter"? It'll
be helpful to other reviewers to recognize
