[JIRA] (JENKINS-35480) Execute shell FATAL: command execution failed
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Sorry, over last months I had no time to work on the plugin, because I had to focus on the Jenkins core and other projects. I also have not been using this plugin on my own since 2016. So I have decided to unassign the issues so that there is no expectation that I work on them anytime soon. Currently the plugin is being transfered to another maintainer. Hopefully he will have some time to finish triaging of the issues and maybe to deliver some fixes. But, as in any community-driven project, everybody is welcome to propose pull requests and to contribute to the plugin's state. Jenkins / JENKINS-35480 Execute shell FATAL: command execution failed Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-35480) Execute shell FATAL: command execution failed
Title: Message Title Rick Liu commented on JENKINS-35480 Re: Execute shell FATAL: command execution failed I have already selected "save parameters to file" but it's still the same Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35480) Execute shell FATAL: command execution failed
Title: Message Title vimil commented on JENKINS-35480 Re: Execute shell FATAL: command execution failed This is because the json data has exceeded the maximum allowed commandline length. You will have to use the 'save json to file' option in extended choice parameter plugin configuration. When you do this a file containing json contents is saved to the job location and its path is passed to the shell instead of the json content itself Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35480) Execute shell FATAL: command execution failed
Title: Message Title
Rick Liu updated an issue
Jenkins / JENKINS-35480
Execute shell FATAL: command execution failed
Change By:
Rick Liu
When use "*Extended Choice Parameter plug-in*" together with "*JSON parameter type*",I'll hit the error below for "*Exeucte Shell*" in "*Promotion process / Action*".When use "*Extended Choice Parameter plug-in*" together with "*Basic Parameter Types*",then everything is ok.Below is the JSON groovy script I'm using:{code}import org.boon.Boon;def jsonEditorOptions = Boon.fromJson(/{disable_edit_json: true,disable_properties: true,no_additional_properties: false,disable_collapse: true,disable_array_add: false,disable_array_delete: false,disable_array_reorder: true,theme: "bootstrap2",iconlib:"bootstrap3",schema: {"type": "object","title": "Coverage Report Generator","properties": { "Report Description": { "type": "string", "propertyOrder": 1, "default": "Description", }, "Build File": { "type": "string", "propertyOrder": 2, "media" : { "binaryEncoding": "base64" }, "options" : { "include_filename": true }, }, "Coverage File": { "type": "string", "propertyOrder": 3, "media" : { "binaryEncoding": "base64" }, "options" : { "include_filename": true }, }, "Diff File": { "type": "string", "propertyOrder": 4, "media" : { "binaryEncoding": "base64" }, "options" : { "include_filename": true }, }, "Extra Coverage Files": { "type": "array", "propertyOrder": 5, "title": "Extra Coverage Files", "format": "table", "uniqueItems": true, "items": { "type": "object", "title": "Coverage Files", "properties": {"File": { "type": "string", "propertyOrder": 1, "media" : { "binaryEncoding": "base64" }, "options" : { "include_filename": true },} } } },}startval: [ ]}/);return jsonEditorOptions;{code} Under "Promotion process / Actions",I add an action "Execute shell" with commands below:{code}#!/bin/bashecho "test!!!"{code}And promotion job is always failed with:{code}[Test_Coverage_Report] $ /bin/bash -xe /tmp/hudson4980267768844983951.shFATAL: command execution failedjava.io.IOException: Cannot run program "/bin/bash" (in directory "/home/devops/jenkins_slave/workspace/ReviewBoard/Test_Coverage_Report"): error=7, Argument list too long at java.lang.ProcessBuilder.start(ProcessBuilder.java:1047) at hudson.Proc$LocalProc.(Proc.java:244) at hudson.Proc$LocalProc.(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:815) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1148) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1113) at hudson.remoting.UserRequest.perform(UserRequest.java:120) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at
[JIRA] (JENKINS-35480) Execute shell FATAL: command execution failed
Title: Message Title Rick Liu commented on JENKINS-35480 Re: Execute shell FATAL: command execution failed Ok I just found out this error happened only when I use "Extended Choice Parameter" plug-in and use "JSON parameter type". If I use "Extended Choice Parameter" plug-in and use "Basic Parameter Types ", then everything works. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35480) Execute shell FATAL: command execution failed
Title: Message Title
Rick Liu updated an issue
Jenkins / JENKINS-35480
Execute shell FATAL: command execution failed
Change By:
Rick Liu
Under "Promotion process / Actions",I add an action "Execute shell" with commands below:{code}#!/bin/bashecho "test!!!"{code}And promotion job is always failed with:{code}[Test_Coverage_Report] $ /bin/bash -xe /tmp/hudson4980267768844983951.shFATAL: command execution failedjava.io.IOException: Cannot run program "/bin/bash" (in directory "/home/devops/jenkins_slave/workspace/ReviewBoard/Test_Coverage_Report"): error=7, Argument list too long at java.lang.ProcessBuilder.start(ProcessBuilder.java:1047) at hudson.Proc$LocalProc.(Proc.java:244) at hudson.Proc$LocalProc.(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:815) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1148) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1113) at hudson.remoting.UserRequest.perform(UserRequest.java:120) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) at ..remote call to jenkins-slave98(172.18.25.208)(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416) at hudson.remoting.UserResponse.retrieve(UserRequest.java:220) at hudson.remoting.Channel.call(Channel.java:781) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:928) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:95) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:64) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.build(Promotion.java:405) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.doRun(Promotion.java:347) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.Run.run(Run.java:1676) at hudson.plugins.promoted_builds.Promotion.run(Promotion.java:286) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Caused by: java.io.IOException: error=7, Argument list too long at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:187) at java.lang.ProcessImpl.start(ProcessImpl.java:130) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1028) at hudson.Proc$LocalProc.(Proc.java:244) at hudson.Proc$LocalProc.(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:815) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at
[JIRA] (JENKINS-35480) Execute shell FATAL: command execution failed
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-35480 Execute shell FATAL: command execution failed Change By: Rick Liu Component/s: extended-choice-parameter-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35480) Execute shell FATAL: command execution failed
Title: Message Title Rick Liu commented on JENKINS-35480 Re: Execute shell FATAL: command execution failed I just added the space between the hash-bang and /bin/bash, but still got error. #! /bin/bash -xe echo "test!!!" [Test_Coverage_Report] $ /bin/bash -xe /tmp/hudson1672939348743230101.sh FATAL: command execution failed java.io.IOException: Cannot run program "" (in directory "/home/devops/jenkins_slave/workspace/ReviewBoard/Test_Coverage_Report"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1047) at hudson.Proc$LocalProc.(Proc.java:244) at hudson.Proc$LocalProc.(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:815) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1148) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1113) at hudson.remoting.UserRequest.perform(UserRequest.java:120) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) at ..remote call to jenkins-slave97(172.16.81.60)(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416) at hudson.remoting.UserResponse.retrieve(UserRequest.java:220) at hudson.remoting.Channel.call(Channel.java:781) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:928) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:95) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:64) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.build(Promotion.java:405) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.doRun(Promotion.java:347) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.Run.run(Run.java:1676) at hudson.plugins.promoted_builds.Promotion.run(Promotion.java:286) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:187) at java.lang.ProcessImpl.start(ProcessImpl.java:130) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1028) at hudson.Proc$LocalProc.(Proc.java:244) at hudson.Proc$LocalProc.(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:815) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1148) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1113) at hudson.remoting.UserRequest.perform(UserRequest.java:120) at
[JIRA] (JENKINS-35480) Execute shell FATAL: command execution failed
Title: Message Title Ahmed AbouZaid commented on JENKINS-35480 Re: Execute shell FATAL: command execution failed I'm aware that you don't have a space, but to clear any confuse. The problem appears when there is a space between hashbang and shell path: #! /bin/bash When I removed it then it works fine. #!/bin/bash Installation: apt Jenkins: 2.7 Tomcat: No Java: 8 oracle (1.8.0_91) System: Ubuntu 14.04.4 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-35480) Execute shell FATAL: command execution failed
Title: Message Title
Ahmed AbouZaid updated an issue
Jenkins / JENKINS-35480
Execute shell FATAL: command execution failed
Change By:
Ahmed AbouZaid
Comment:
I have the same issue.{code}Installation: aptJenkins: 2.9Tomcat: NoJava: 8 oracle (1.8.0_91)System: Ubuntu 14.04.4{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35480) Execute shell FATAL: command execution failed
Title: Message Title Ahmed AbouZaid commented on JENKINS-35480 Re: Execute shell FATAL: command execution failed I have the same issue. Installation: apt Jenkins: 2.9 Tomcat: No Java: 8 oracle (1.8.0_91) System: Ubuntu 14.04.4 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
