[ 
https://issues.jenkins-ci.org/browse/JENKINS-12108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159356#comment-159356
 ] 

Javier Berrocal commented on JENKINS-12108:
-------------------------------------------

This issue has happen to me again today when I've upgraded to version 1.26 of 
the EnvInject plugin

I've rolled back to previous version 1.20 and things are working fine again.

Current Jenkins version: Jenkins ver. 1.451
                
> EnvInject failure using multi-configuration jobs
> ------------------------------------------------
>
>                 Key: JENKINS-12108
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12108
>             Project: Jenkins
>          Issue Type: Bug
>          Components: envinject
>    Affects Versions: current
>         Environment: Debian 5.0
>            Reporter: Thomas Wood
>            Assignee: gbois
>            Priority: Critical
>
> We recently upgraded to 1.424.1 LTS, and switched to the EnvInject plugin 
> instead of the deprecated "Hudson SetEnv" plugin to set environment variables 
> for our jobs.
> All our multi-configuration jobs are now failing:
> [EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting 
> env vars as a build step: hudson.matrix.MatrixConfiguration cannot be cast to 
> hudson.model.TopLevelItem
> This is easy to reproduce:
> - Install EnvInject
> - Create a new multiconfiguration job
> - Add an axis named "axis" with the values "a b c"
> - Add an execute shell build step consisting of "echo $axis"
> - Save and run the job (it should execute successfully against three 
> configurations)
> - Now, edit the job and check "Inject environment variables to the build 
> process" in the Build Environment section.  You don't actually need to add 
> any properties content to reproduce the problem--just check the checkbox.
> - Run the job again.  All three configurations fail.
> This is a big problem for us as all our multi-configuration jobs also use 
> environment variables.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to