[JIRA] [ivy] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Dmitry Danilson commented on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used Note that the variable in the file name was not expanded properly. Looks like it is the root of the issue: environment variables are not passed to slave. As it was explained in this perfect comment it appears that Jenkins "Environment Variables" are not in fact environment variables - they should be called "Custom Jenkins Slave Parameters". As you could see here there is no variable called JAVA_VERSION among these so called "Environment Variables" (though they are not environment variables). So in order to get this fixed, you should define JAVA_VERSION variable using EnvInject plugin to get it injected into slave environment. I guess it should fix the issue. Let me know if it does not. 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.
[JIRA] [ivy] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Dmitry Danilson edited a comment on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used Note that the variable in the file name was not expanded properly. Looks like it is the root of the issue: environment variables are not passed to slave. As it was explained in this perfect comment it appears that Jenkins "Environment Variables" are not in fact environment variables - they should be called "Custom Jenkins Slave Parameters". As you could see here there is no variable called JAVA_VERSION among these so called "Environment Variables" (though they are not environment variables). So in order to get this fixed, you should define JAVA_VERSION variable using EnvInject plugin to get it injected into slave environment. See also related issues at StackOverflow: http://stackoverflow.com/questions/5818403/jenkins-hudson-environment-variables http://stackoverflow.com/questions/10625259/how-to-set-environment-variables-in-jenkins I guess it should fix the issue. Let me know if it does not. 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.
[JIRA] [ivy] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Gregory Boissinot updated JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used Change By: Gregory Boissinot (21/May/13 4:48 PM) Component/s: envinject 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.
