--- Quote Start ---
I have tried it but it didn't work. Jenkins does import environment variables from windows but my script is running in a bare bone bash shell that is not initialized by a bashrc. it won't have reference to what windows or Jenkins has defined.
The nios2eds command line has no problem so it must somehow be initialized with the license info in a way other than LM_LISCENCE_FILE, maybe there is more in the initialization process of the bash shell than the bashrc file?
--- Quote End ---
When a new process is created in an operating system, it can inherit environment variables from the parent process. For example, when I run Cygwin, the shell will contain the variables I define as Windows environment variables, and then any 'extra' variables I define in a bashrc file, however, that bashrc file is optional.
When you say "Jenkins" I assume you mean this tool:
http://en.wikipedia.org/wiki/jenkins_%28software%29 I've never used this tool, but it sounds like Java may be responsible for starting your bash process. Perhaps its not setting the environment properly.
If you can print a message from your bash shell, create a Jenkins run that simply prints an environment variable. Try it under Linux and Windows and see if you get the same response. Try starting the Jenkins tool from the shell where you know the environment variable you are printing definitely exists. If the bash shell run from Jenkins can't see that variable, then its a problem with Jenkins.
I'd recommending finding a forum where people know about Jenkins ... personally, this is the first time I've heard of it.
Cheers,
Dave
Honored Contributor
