-
Bug
-
Resolution: Unresolved
-
Major
-
None
Hi loghijiaha,
I'm debugging the plug-in just to have one final look at the code as we are near the end of GSoC.
While doing so, I found what seems to be a bug.
My job has several build steps, one for JS, one for Python, etc. The one for JS triggers the following pre-command, which I think is being used to change the working directory.
import os os.chdir('/home/kinow/Development/java/jenkins/machine-learning-plugin/work/workspace/e2e-1')
That results in an error, that is logged as "ERROR'. I tested using `%%python` in a notebook cell, while using the same javascript kernel, but it still failed to run. This command only works when I select the Python kernel.
I wonder if there is no way to tell Zeppelin what is the working directory we want to use, before starting the kernel?
- links to
[JENKINS-63452] For every kernel, the plug-in tries to run Python code, which could fail if language is not Python
| Description |
New:
Hi [~loghijiaha], I'm debugging the plug-in just to have one final look at the code as we are near the end of GSoC. While doing so, I found what seems to be a bug. My job has several build steps, one for JS, one for Python, etc. The one for JS triggers the following pre-command, which I think is being used to change the working directory. {code:java} import os os.chdir('/home/kinow/Development/java/jenkins/machine-learning-plugin/work/workspace/e2e-1') {code} That results in an error, that is logged as "ERROR'. I tested using `%%python` in a notebook cell, while using the same javascript kernel, but it still failed to run. This command only works when I select the Python kernel. I wonder if there is no way to tell Zeppelin what is the working directory we want to use, before starting the kernel? |
| Remote Link | New: This issue links to "PR for setting working directory (Web Link)" [ 25703 ] |