Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-22183

Custom-tools plugin breaks environment for 'Execute Windows batch command'

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • customtools-plugin
    • None
    • Windows 2008

      Behavior seems node specific, we have old node and same job runs fine on this node with and without Install Custom Tools enabled, but on new node seems if Install Custom Tools is enabled in the project, then 'Execute Windows batch command' build step fails:
      [CustomTools] - Handle: Starting installation
      [CustomTools] - Handle: Label specifics from 'windows' will be applied
      [CustomTools] - Handle: Tool is installed at C:\CI\Jenkins\tools\com.cloudbees.jenkins.plugins.customtools.CustomTool\Handle
      [CustomTools] - Handle: Setting Handle_HOME=C:\CI\Jenkins\tools\com.cloudbees.jenkins.plugins.customtools.CustomTool\Handle
      [EnvInject] - Loading node environment variables.
      Building remotely on gimci-vm8 in workspace C:\CI\Jenkins\workspace\test-py-install
      [test-py-install] $ cmd /c call C:\Windows\TEMP\hudson4013721381829777457.bat
      The parameter is incorrect
      FATAL: command execution failed
      java.io.IOException: Cannot run program "cmd" (in directory "C:\CI\Jenkins\workspace\test-py-install"): CreateProcess error=87, The parameter is incorrect
      at java.lang.ProcessBuilder.start(Unknown Source)
      ...
      at java.lang.Thread.run(Unknown Source)
      Caused by: java.io.IOException: CreateProcess error=87, The parameter is incorrect
      at java.lang.ProcessImpl.create(Native Method)
      at java.lang.ProcessImpl.<init>(Unknown Source)
      at java.lang.ProcessImpl.start(Unknown Source)
      ... 16 more
      Build step 'Execute Windows batch command' marked build as failure
      Finished: FAILURE

        1. config.xml
          2 kB
        2. failed-build-injectedEnvVars.txt
          3 kB
        3. failed-build-log
          2 kB
        4. no-custom-tools-injectedEnvVars.txt
          3 kB
        5. no-custom-tools-log
          3 kB

          [JENKINS-22183] Custom-tools plugin breaks environment for 'Execute Windows batch command'

          Alexey Trenikhin created issue -

          Oleg Nenashev added a comment -

          The issue may be caused by the EnvInject plugin.
          JENKINS-15475 seems to be a very related bug.

          Could you run the job without EnvInject?
          If it does not help, please provide your versions of [Jenkins Core/slave.jar/Custom tools/EnvInject].

          Oleg Nenashev added a comment - The issue may be caused by the EnvInject plugin. JENKINS-15475 seems to be a very related bug. Could you run the job without EnvInject? If it does not help, please provide your versions of [Jenkins Core/slave.jar/Custom tools/EnvInject] .

          Alexey Trenikhin added a comment -

          I can’t run without EnvInject, seems I can’t disable it at job level, and can’t uninstall because it will effect other users.
          Envinject: 1.89
          custom-tools-plugin: 0.4.1
          Slave.jar version: 2.33
          Jenkins ver. 1.542

          Alexey Trenikhin added a comment - I can’t run without EnvInject, seems I can’t disable it at job level, and can’t uninstall because it will effect other users. Envinject: 1.89 custom-tools-plugin: 0.4.1 Slave.jar version: 2.33 Jenkins ver. 1.542

          Oleg Nenashev added a comment -

          You can just create a job's clone without script contents. They should not affect the issue. I suggest to start from a "Hello, world!" job with a Batch Command build step and the tool installation.

          If you provide the job's configuration, I'll try to provide more advices. Most probable, it won't be possible to reproduce the issue without your host, so I rely on your help during the testing

          BTW, the information about your target node could be useful as well.

          Oleg Nenashev added a comment - You can just create a job's clone without script contents. They should not affect the issue. I suggest to start from a "Hello, world!" job with a Batch Command build step and the tool installation. If you provide the job's configuration, I'll try to provide more advices. Most probable, it won't be possible to reproduce the issue without your host, so I rely on your help during the testing BTW, the information about your target node could be useful as well.

          Alexey Trenikhin added a comment -

          Job already "hello world" style, just instead of "Hello, world" it prints out environment
          I'm attaching config, injectedEnvVars and log files for run without custom-tools and with custom tools

          Alexey Trenikhin added a comment - Job already "hello world" style, just instead of "Hello, world" it prints out environment I'm attaching config, injectedEnvVars and log files for run without custom-tools and with custom tools

          Alexey Trenikhin added a comment -

          config file with custom tools

          Alexey Trenikhin added a comment - config file with custom tools
          Alexey Trenikhin made changes -
          Attachment New: config.xml [ 25555 ]

          Alexey Trenikhin added a comment -

          injectedEnvVars file for run with custom-tools

          Alexey Trenikhin added a comment - injectedEnvVars file for run with custom-tools
          Alexey Trenikhin made changes -
          Attachment New: failed-build-injectedEnvVars.txt [ 25556 ]

          Alexey Trenikhin added a comment -

          log for run with custom-tools

          Alexey Trenikhin added a comment - log for run with custom-tools
          Alexey Trenikhin made changes -
          Attachment New: failed-build-log [ 25557 ]

            Unassigned Unassigned
            alexeyt Alexey Trenikhin
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: