Hello, I'm looking to provide environment setup based on an OpenEmbedded environment shell script which is sourced prior to build. Normally, this is as easy as source ./env.sh in the shell windows, but there is a wrinkle here. I would like to use the KlockWork plugin for this specific build, because running KW in the shell boxes makes the output difficult to manage. Note that the plugin isn't my problem. It's how to make Jenkins persist an environment. Here is my setup and a better description.
<in several Jenkins Execute Shell Box in a Free Style Project> Unpack OE SDK tarball git clone my repository source the SDK .sh file to create the cross environment make This works fine. To include KlockWork, I either have to run the same above, but use kwshell make as the last step to get KW to interpret results, or, I can use the KW plugin to run the commands for me. But the KW pluigin doesn't inherit env variables from a shell I can control per build, so I can't setup the cross environment before the plugin runs. I have looked into EnvInject, but I don't see a way to simply source a shell script using this plugin. I may be missing something though. I cannot make the cross environment permanent to Jenkins because we have other builds running on the same machine that setup their own environment in shell boxes. Plus, if the cross environment changes, someone would have to know how to fix it. Does anyone know how to run a 'source env.sh" prior to running commands such that all commands and shell boxes inherit this by default? Any help would be very much appreciated. Thank you. Pete -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
