[JIRA] (JENKINS-12108) EnvInject failure using multi-configuration jobs

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-12108) EnvInject failure using multi-configuration jobs

JIRA noreply@jenkins-ci.org
Thomas Wood created JENKINS-12108:
-------------------------------------

             Summary: 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-12108) EnvInject failure using multi-configuration jobs

JIRA noreply@jenkins-ci.org

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

gbois resolved JENKINS-12108.
-----------------------------

    Resolution: Fixed

EnvInject 1.1 fixes the bug.
Thanks
               

> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-12108) EnvInject failure using multi-configuration jobs

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-12108) EnvInject failure using multi-configuration jobs

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

Javier Berrocal reopened JENKINS-12108:
---------------------------------------


Issue happens for version 1.26
               

> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-12108) EnvInject failure using multi-configuration jobs

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

Javier Berrocal edited comment on JENKINS-12108 at 2/22/12 11:46 AM:
---------------------------------------------------------------------

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

From console output:

[EnvInject] - Executing scripts and injecting environment variables after the SCM step.
[EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build wrap: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem

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

Current Jenkins version: Jenkins ver. 1.451
               
      was (Author: javierb):
    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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-12108) EnvInject failure using multi-configuration jobs

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

JavierB edited comment on JENKINS-12108 at 2/22/12 11:48 AM:
-------------------------------------------------------------

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

From console output:

[EnvInject] - Executing scripts and injecting environment variables after the SCM step.
[EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build wrap: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem

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

Current Jenkins version: Jenkins ver. 1.451 [under Ubuntu]
               
      was (Author: javierb):
    This issue has happened to me again today when I've upgraded to version 1.26 of the EnvInject plugin

From console output:

[EnvInject] - Executing scripts and injecting environment variables after the SCM step.
[EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build wrap: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem

I've rolled back to previous version 1.25 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-12108) EnvInject failure using multi-configuration jobs

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

JavierB edited comment on JENKINS-12108 at 2/22/12 11:47 AM:
-------------------------------------------------------------

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

From console output:

[EnvInject] - Executing scripts and injecting environment variables after the SCM step.
[EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build wrap: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem

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

Current Jenkins version: Jenkins ver. 1.451
               
      was (Author: javierb):
    This issue has happen to me again today when I've upgraded to version 1.26 of the EnvInject plugin

From console output:

[EnvInject] - Executing scripts and injecting environment variables after the SCM step.
[EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build wrap: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem

I've rolled back to previous version 1.25 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-12108) EnvInject failure using multi-configuration jobs

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

JavierB edited comment on JENKINS-12108 at 2/22/12 11:59 AM:
-------------------------------------------------------------

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

From console output:

[EnvInject] - Executing scripts and injecting environment variables after the SCM step.
[EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build wrap: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem

I've rolled back to previous version [1.25|http://mirrors.jenkins-ci.org/plugins/envinject/1.25/] and things are working fine again.

Current Jenkins version: Jenkins ver. 1.451 [under Ubuntu]
               
      was (Author: javierb):
    This issue has happened to me again today when I've upgraded to version 1.26 of the EnvInject plugin

From console output:

[EnvInject] - Executing scripts and injecting environment variables after the SCM step.
[EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build wrap: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem

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

Current Jenkins version: Jenkins ver. 1.451 [under Ubuntu]
                 

> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-12108) EnvInject failure using multi-configuration jobs

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

JavierB edited comment on JENKINS-12108 at 2/22/12 11:59 AM:
-------------------------------------------------------------

This issue has happened to me again today when I've upgraded to version [1.26|http://mirrors.jenkins-ci.org/plugins/envinject/1.26/] of the EnvInject plugin

From console output:

[EnvInject] - Executing scripts and injecting environment variables after the SCM step.
[EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build wrap: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem

I've rolled back to previous version [1.25|http://mirrors.jenkins-ci.org/plugins/envinject/1.25/] and things are working fine again.

Current Jenkins version: Jenkins ver. 1.451 [under Ubuntu]
               
      was (Author: javierb):
    This issue has happened to me again today when I've upgraded to version 1.26 of the EnvInject plugin

From console output:

[EnvInject] - Executing scripts and injecting environment variables after the SCM step.
[EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build wrap: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem

I've rolled back to previous version [1.25|http://mirrors.jenkins-ci.org/plugins/envinject/1.25/] and things are working fine again.

Current Jenkins version: Jenkins ver. 1.451 [under Ubuntu]
                 

> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-12108) EnvInject failure using multi-configuration jobs

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

JavierB edited comment on JENKINS-12108 at 2/22/12 11:59 AM:
-------------------------------------------------------------

Issue happens for version [1.26|http://mirrors.jenkins-ci.org/plugins/envinject/1.26/]
               
      was (Author: javierb):
    Issue happens for version 1.26
                 

> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-12108) EnvInject failure using multi-configuration jobs

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

JavierB edited comment on JENKINS-12108 at 2/22/12 1:47 PM:
------------------------------------------------------------

Issue happens for latest versions [1.26|http://mirrors.jenkins-ci.org/plugins/envinject/1.26/] and [1.27|http://mirrors.jenkins-ci.org/plugins/envinject/1.27/]
               
      was (Author: javierb):
    Issue happens for version [1.26|http://mirrors.jenkins-ci.org/plugins/envinject/1.26/]
                 

> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-12108) EnvInject failure using multi-configuration jobs

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

gbois resolved JENKINS-12108.
-----------------------------

    Resolution: Fixed
   

> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-12108) EnvInject failure using multi-configuration jobs

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

Mikel Perez reopened JENKINS-12108:
-----------------------------------


The same issue happens (multi-configuration jobs) after upgrading jenkins from 1.448 to 1.456 and this plugin from 1.31 to 1.40(1.41 & 1.42)

               

> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-12108) EnvInject failure using multi-configuration jobs

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

SCM/JIRA link daemon commented on JENKINS-12108:
------------------------------------------------

Code changed in jenkins
User: Gregory Boissinot
Path:
 src/main/java/org/jenkinsci/plugins/envinject/EnvInjectListener.java
http://jenkins-ci.org/commit/envinject-plugin/6d5641bf91a569f9a37e4881b84170ce0834856f
Log:
  Fix JENKINS-12108





               

> 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 | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-12108) EnvInject failure using multi-configuration jobs

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

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

gbois resolved JENKINS-12108.
-----------------------------

    Resolution: Fixed
   

> 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

       
Loading...