|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
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/groups/opt_out.
These commands :
"tar xvzf tools/hudson.model.JDK/java7/jdk.sh"
Means that during the build you are trying to extract a shell script with tar instead of running it.
And the error messages say that shell script is not present anyway.
Try using the Jenkins config options to auto install Java OR add a line to your slave's init script section "yum -y install jdk"
(where you replace jdk with a proper name of a package containing the java7 jdk. Or do your RPM installation)
The tools directory will not necessarily all be copied from your existing jenkins to the new instance unless you included it in the AMI.
But you said the AMI had already got Java7 installed as root from an RPM, so you shouldn't even need to install the JDK again. My ec2 plugin does not try to install jdk7 which suggests this error is coming either from your build script or some other config option somewhere (maybe you specify a JVM in the build options).