Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
custom-tools 0.4, android emulator plugin
Description
I run customtools-plugin together with android-emulator-plugin, and when jenkins launches tasks for android-emulator, they are launched without the default PATH varable.
This means that the shell scripts that start the emulator can't find common tools as dirname, file and so on.
Workaround is to add a custom tool that defines default paths too, but thats site-wide and when some nodes have other PATH's than other, i can only add the directories that exists on all nodes.
Attachments
Issue Links
- is blocking
-
JENKINS-20560 Custom-tools plugin breaks path for android-emulator
-
- Closed
-
- is duplicated by
-
JENKINS-19086 NullPointerException on ProcStarter.envs (Launcher.java:302)
-
- Closed
-
- is related to
-
JENKINS-20559 hudson.Launcher:ProcStarter::envs() may throw NPE
-
- Resolved
-
pull/11 solves all blocking bugs.
The part with the default path being emptied is still there, so it fails as shown in error-custom-tools-0.5-snap-with-platform-tools.txt, but i currently workaround that by adding a custom-tool, DEFAULT_PATH which exports the default path.
It would be neat to get that one fixed to.