-
Bug
-
Resolution: Fixed
-
Major
-
Jenkins 1.509.3 - 1.537
ProcStarter::envs() calls envs.clone(), but does not check envs variable for null. BTW, the variable may be null in the following case (see JENKINS-19506):
- There are several wrappers
- One of wrappers triggers remote call (Launcher::launch()) in setUp() or decorateLauncher() methods to setup variables (example: android-emulator) => it will make all other launchers to provide their environment variables
- One of other wrappers retrieves ProcStarter.envs() in setUp() or decorateLauncher()
- envs are empty for nested call => execution of other wrapper causes NPE inside core
- is duplicated by
-
JENKINS-19086 NullPointerException on ProcStarter.envs (Launcher.java:302)
-
- Closed
-
- is related to
-
JENKINS-19506 [integration] - android-plugin + custom-tools installation fails due to NPE in ProcStarter::envs()
-
- Closed
-
[JENKINS-20559] hudson.Launcher:ProcStarter::envs() may throw NPE
Link |
New:
This issue is related to |
Link |
New:
This issue is duplicated by |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Labels | Original: launcher | New: launcher lts-candidate |
Labels | Original: launcher lts-candidate | New: 1.565.1-fixed launcher |
Workflow | Original: JNJira [ 152084 ] | New: JNJira + In-Review [ 194203 ] |