Quantcast

Upgrading to v1.473 has broken all my matrix jobs

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

Upgrading to v1.473 has broken all my matrix jobs

tfields
Hi there,

I just upgraded to Jenkins 1.473 and I'm getting this for all my matrix jobs:

SEVERE: Failed Loading job PhyreAssetPacker-Live java.lang.NullPointerException at hudson.matrix.MatrixProject.updateTransientActions(MatrixProject.java:431) at hudson.model.AbstractProject.onLoad(AbstractProject.java:296) at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:466) at hudson.model.Items.load(Items.java:115) at jenkins.model.Jenkins$17.run(Jenkins.java:2492) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:878) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)

Anyone know what the problem might be?

Cheers,
Tom.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Upgrading to v1.473 has broken all my matrix jobs

tfields
I just spotted https://issues.jenkins-ci.org/browse/JENKINS-14273. Please fix asap.

On Monday, 2 July 2012 11:37:30 UTC+1, Thomas Fields wrote:
Hi there,

I just upgraded to Jenkins 1.473 and I'm getting this for all my matrix jobs:

SEVERE: Failed Loading job PhyreAssetPacker-Live java.lang.NullPointerException at hudson.matrix.MatrixProject.updateTransientActions(MatrixProject.java:431) at hudson.model.AbstractProject.onLoad(AbstractProject.java:296) at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:466) at hudson.model.Items.load(Items.java:115) at jenkins.model.Jenkins$17.run(Jenkins.java:2492) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:878) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)

Anyone know what the problem might be?

Cheers,
Tom.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

RE: Upgrading to v1.473 has broken all my matrix jobs

Matthew.Webber

What version did you upgrade from? Looking at the change log, there was a change relating to matrix projects in 1.472, but not 1.473.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Thomas Fields
Sent: 02 July 2012 11:39
To: [hidden email]
Subject: Re: Upgrading to v1.473 has broken all my matrix jobs

 

I just spotted https://issues.jenkins-ci.org/browse/JENKINS-14273. Please fix asap.

On Monday, 2 July 2012 11:37:30 UTC+1, Thomas Fields wrote:

Hi there,

I just upgraded to Jenkins 1.473 and I'm getting this for all my matrix jobs:

SEVERE: Failed Loading job PhyreAssetPacker-Live
java.lang.NullPointerException
        at hudson.matrix.MatrixProject.updateTransientActions(MatrixProject.java:431)
        at hudson.model.AbstractProject.onLoad(AbstractProject.java:296)
        at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:466)
        at hudson.model.Items.load(Items.java:115)
        at jenkins.model.Jenkins$17.run(Jenkins.java:2492)
        at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
        at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
        at jenkins.model.Jenkins$7.runTask(Jenkins.java:878)
        at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
        at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)

Anyone know what the problem might be?

Cheers,
Tom.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Upgrading to v1.473 has broken all my matrix jobs

tfields
I'm running Jenkins v1.472 now and it's working fine. 

On Monday, 2 July 2012 11:42:30 UTC+1, (unknown) wrote:

What version did you upgrade from? Looking at the change log, there was a change relating to matrix projects in 1.472, but not 1.473.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Thomas Fields
Sent: 02 July 2012 11:39
To: [hidden email]
Subject: Re: Upgrading to v1.473 has broken all my matrix jobs

 

I just spotted https://issues.jenkins-ci.org/browse/JENKINS-14273. Please fix asap.

On Monday, 2 July 2012 11:37:30 UTC+1, Thomas Fields wrote:

Hi there,

I just upgraded to Jenkins 1.473 and I'm getting this for all my matrix jobs:

SEVERE: Failed Loading job PhyreAssetPacker-Live
java.lang.NullPointerException
        at hudson.matrix.MatrixProject.updateTransientActions(MatrixProject.java:431)
        at hudson.model.AbstractProject.onLoad(AbstractProject.java:296)
        at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:466)
        at hudson.model.Items.load(Items.java:115)
        at jenkins.model.Jenkins$17.run(Jenkins.java:2492)
        at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
        at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
        at jenkins.model.Jenkins$7.runTask(Jenkins.java:878)
        at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
        at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)

Anyone know what the problem might be?

Cheers,
Tom.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Global env vars not usable in parameterized build?

Noah Hoffman
In reply to this post by tfields
Hi All,

    I'm setting some environment variables in the Jenkins Master (Manage Jenkins > Configure System > Global Properties) but, using the parameterized build plugin, I'm setting up some new string variables and wanting to use these global vars as the default values but it doesn't seem to work.  Can anyone confirm that this is indeed a bug or there's a better/different way to achieve this goal?

Thanks,
Noah
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Global env vars not usable in parameterized build?

Akiko Takano
Hello.

First, let me confirm is  "parameterized build plugin" the same to
"parameterized trigger plugin" or not?
(https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin)

Please forgive me if I have misunderstanding.

Then, I can pass Global environment variables to  other project which
triggered by Parameterized Trigger Plugin.

For example:
1. Set Global parameters:  GLOBAL_VAR=hoo
2. Create some upstream job. (Job-A)
3. Create downstream job. (Job-B)
    - This has a shell task like "echo ${PARAM_FOR_JOB-B}".

3. At the Job-A configuration, add post build task with using "Trigger
parametarized build other project"
4. Set Job-B as "Projects to build".
5. Use "Predefined parameters" as parametere to pass, and set like this:

        PARAM_FOR_JOB-B=${GLOBAL_BAR}

How about?


2012/9/20 Noah Hoffman <[hidden email]>:

> Hi All,
>
>
>     I'm setting some environment variables in the Jenkins Master (Manage
> Jenkins > Configure System > Global Properties) but, using the
> parameterized
> build plugin, I'm setting up some new string variables and wanting to use
> these global vars as the default values but it doesn't seem to work.  Can
> anyone confirm that this is indeed a bug or there's a better/different way
> to achieve this goal?
>
> Thanks,
> Noah
Loading...