• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • maven-plugin
    • None
    • Platform: All, OS: Linux

      On Linux, if two variables path and PATH environment variables are set. Then
      builds on maven will fail with an error "env: not found" see stack trace below.
      Apparently PATH is ignored and path is used to launch maven.

      [webstickCore] $ /exec/products/jdk1.5.0_16/bin/java -cp
      /exec/products/tomcat_hudson/webapps/hudson/WEB-INF/lib/maven-agent-1.262.jar:/exec/products/maven/boot/classworlds-1.1.jar
      hudson.maven.agent.Main /exec/products/maven
      /exec/products/tomcat_hudson/webapps/hudson/WEB-INF/lib/remoting-1.262.jar
      /exec/products/tomcat_hudson/webapps/hudson/WEB-INF/lib/maven-interceptor-1.262.jar
      39693
      channel started
      Executing Maven: -B -B -f
      /data/hudson/jobs/webstickCore/workspace/webstickCore/pom.xml clean
      Error getting environment vars for profile activation: java.io.IOException:
      java.io.IOException: env: not found
      [WARNING] Failed to initialize environment variable resolver. Skipping
      environment substitution in settings.
      [WARNING] Failed to initialize environment variable resolver. Skipping
      environment substitution in settings.
      channel stopped
      ERROR: Failed to parse POMs
      hudson.util.IOException2
      at hudson.maven.MavenBuilder.call(MavenBuilder.java:188)
      at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:542)
      at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:488)
      at hudson.remoting.UserRequest.perform(UserRequest.java:69)
      at hudson.remoting.UserRequest.perform(UserRequest.java:23)
      at hudson.remoting.Request$2.run(Request.java:213)
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
      at java.util.concurrent.FutureTask.run(FutureTask.java:123)
      at
      java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
      at java.lang.Thread.run(Thread.java:595)
      Caused by: java.lang.reflect.InvocationTargetException
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at
      sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:585)
      at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
      at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
      at hudson.maven.agent.Main.launch(Main.java:134)
      at hudson.maven.MavenBuilder.call(MavenBuilder.java:139)
      ... 11 more
      Caused by: java.io.IOException: java.io.IOException: env: not found
      at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
      at java.lang.ProcessImpl.start(ProcessImpl.java:65)
      at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
      at java.lang.Runtime.exec(Runtime.java:591)
      at java.lang.Runtime.exec(Runtime.java:429)
      at java.lang.Runtime.exec(Runtime.java:326)
      at
      hidden.org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars(CommandLineUtils.java:250)
      at
      hidden.org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars(CommandLineUtils.java:216)
      at
      org.apache.maven.project.interpolation.RegexBasedModelInterpolator.<init>(RegexBasedModelInterpolator.java:63)
      at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
      at
      sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
      at
      sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
      at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
      at java.lang.Class.newInstance0(Class.java:350)
      at java.lang.Class.newInstance(Class.java:303)
      at
      org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:44)
      at
      org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464)
      at
      org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:93)
      at
      org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:92)
      at
      org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331)
      at
      org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:129)
      at
      org.codehaus.plexus.component.composition.FieldComponentComposer.assembleComponent(FieldComponentComposer.java:73)
      at
      org.codehaus.plexus.component.composition.DefaultComponentComposerManager.assembleComponent(DefaultComponentComposerManager.java:68)
      at
      org.codehaus.plexus.DefaultPlexusContainer.composeComponent(DefaultPlexusContainer.java:1486)
      at
      org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:29)
      at
      org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:101)
      at
      org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:105)
      at
      org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:95)
      at
      org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:92)
      at
      org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331)
      at
      org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:129)
      at
      org.codehaus.plexus.component.composition.FieldComponentComposer.assembleComponent(FieldComponentComposer.java:73)
      at
      org.codehaus.plexus.component.composition.DefaultComponentComposerManager.assembleComponent(DefaultComponentComposerManager.java:68)
      at
      org.codehaus.plexus.DefaultPlexusContainer.composeComponent(DefaultPlexusContainer.java:1486)
      at
      org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:29)
      at
      org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:101)
      at
      org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:105)
      at
      org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:95)
      at
      org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:92)
      at
      org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331)
      at org.codehaus.plexus.embed.Embedder.lookup(Embedder.java:78)
      at org.apache.maven.cli.MavenCli.createMavenInstance(MavenCli.java:479)
      at org.apache.maven.cli.MavenCli.main(MavenCli.java:262)
      ... 19 more
      finished: FAILURE

          [JENKINS-2687] case sensitive environment variable PATH

          Ulli Hafner added a comment -

          Seems not related to the checkstyle plug-in.

          Ulli Hafner added a comment - Seems not related to the checkstyle plug-in.

          Guillaume Missonnier added a comment - - edited

          Got the case sensitive environment variable problem too.

          For instance, if I set these two variable in my slave agent environment :

          #!/bin/bash
          export TEST=TEST
          export test=test
          
          exec java -jar slave.jar
          

          My builds got the following in their environment :

          test=TEST

          Guillaume Missonnier added a comment - - edited Got the case sensitive environment variable problem too. For instance, if I set these two variable in my slave agent environment : #!/bin/bash export TEST=TEST export test=test exec java -jar slave.jar My builds got the following in their environment : test=TEST

            kenliu kenliu
            vergnes vergnes
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: