• Type: Bug
• Resolution: Not A Defect
• Priority: Blocker
• Component/s: component
• Labels:

  None
• Environment:

  Solaris

[JENKINS-31642] Getting "is not an identifier" error in a job

Collapse comment: Mark Waite added a comment - 2015-11-19 02:57

Mark Waite added a comment - 2015-11-19 02:57

The "is not an identifier" is likely an indication that your script is trying to both assign to JAVA_HOME and export in the same line, but the shell which is executing the script does not understand that syntax.

Even if that is not the case, I suspect that "abc.sh" is a script which you control, so you'll need to debug it rather than submitting a Jenkins bug report.

You might try placing "#! /bin/bash" or "#! /bin/ksh" as the first line of your script, in case the default shell that is executing the script doesn't have the capabilities you need.

Expand comment: Mark Waite added a comment - 2015-11-19 02:57

Mark Waite added a comment - 2015-11-19 02:57 The "is not an identifier" is likely an indication that your script is trying to both assign to JAVA_HOME and export in the same line, but the shell which is executing the script does not understand that syntax. Even if that is not the case, I suspect that "abc.sh" is a script which you control, so you'll need to debug it rather than submitting a Jenkins bug report. You might try placing "#! /bin/bash" or "#! /bin/ksh" as the first line of your script, in case the default shell that is executing the script doesn't have the capabilities you need.