EnvInject "Prepare an environment for the run" fails with "SEVERE ERROR"

[David Clark]

Hello,

Having a problem with some basic functionality of the EnvInject plugin.

Adding a simple "Properties Content" to the "Prepare an environment for the run" item causes the plugin to fail with the error below.

The same happens with no script specified, just the checkbox checked.

The same content works just fine when used at the "Inject environment variables to the build process" step.

Here is the build log:

Started by user anonymous

[EnvInject] - Loading node environment variables.

[EnvInject] - Preparing an environment for the build.

[EnvInject] - Keeping Jenkins system variables.

[EnvInject] - Keeping Jenkins build variables.

[EnvInject] - Injecting as environment variables the properties content 

MyVariable=someValue

[EnvInject] - Variables injected successfully.

[EnvInject] - Injecting contributions.

[EnvInject] - [ERROR] - SEVERE ERROR occurs: null

Build step 'Upload to HockeyApp' marked build as failure

Finished: FAILURE

Thanks.

--

David

[Schalk Cronjé]

What is in your properties file and what OS is it executing on?

[David Clark]

I am not using a file I have specified the content as:

MyVariable=someValue

I also get the same problem if there is nothing specified for content.

This is on OSX Mountain Lion (10.8.3)

--

David

On 08/05/2013, at 11:32 PM, Schalk Cronjé <ysb...@gmail.com> wrote:

What is in your properties file and what OS is it executing on?

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/E6BZ1H2Lhzc/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Jerry]

I have not seen the same issue, David. However, on a Windows build slave, the environment variable I specify reports that it was set successfully, but it is not set to my value in later steps.

I've been able to get around the issue by using an older version of the plugin, in my case, 1.33.

-- Jerry

[Jerry]

[korm...@gmail.com]

Have you looked in the Jenkins system log?

When this happened to me I restarted the master and the problem went away and hasn't come back. The problem effected every job that used the EnvInject plugin. I'm not sure what caused it.

Kevin

[rakhee Kulkarni]

It works for David on windows, mac, and ubuntu. I would look in the logs.