• Type: Bug
• Resolution: Unresolved
• Priority: Blocker
• Component/s: envinject-plugin
• Labels:

  None
• Environment:

  Jenkins 1.486
  Plugin 1.72
  Solaris

[JENKINS-15611] Builds launched programmatically via Queue.schedule() fail with error

Collapse comment: Roland Gruber added a comment - 2013-05-13 13:51

Roland Gruber added a comment - 2013-05-13 13:51

Any news on this one or any workaround? This makes the plugin useless for us because jobs fail even if EnvInject is not enabled for them.

Expand comment: Roland Gruber added a comment - 2013-05-13 13:51

Roland Gruber added a comment - 2013-05-13 13:51 Any news on this one or any workaround? This makes the plugin useless for us because jobs fail even if EnvInject is not enabled for them.

Collapse comment: Gregory Boissinot added a comment - 2013-05-13 22:37

Gregory Boissinot added a comment - 2013-05-13 22:37

I'm sorry for my late reply.
I don't know why you have this error. Could you test for now with the latest version?
Do you have any excpetion stack traces in the Jenkins log?

Expand comment: Gregory Boissinot added a comment - 2013-05-13 22:37

Gregory Boissinot added a comment - 2013-05-13 22:37 I'm sorry for my late reply. I don't know why you have this error. Could you test for now with the latest version? Do you have any excpetion stack traces in the Jenkins log?

Collapse comment: Roland Gruber added a comment - 2013-05-14 07:06

Roland Gruber added a comment - 2013-05-14 07:06

We already use version 1.85. Unfortunately, there is no stack trace in Jenkins log or build output.

This is the build output:

Started
[EnvInject] - Loading node environment variables.
[EnvInject] - [ERROR] - SEVERE ERROR occurs: null
Finished: FAILURE

We start the build by our own plugin like this: Jenkins.getInstance().getQueue().schedule(job, job.getDelay(req), parametersAction);
parametersAction is a new object that only contains our own parameters. Do you depend on any values in this object?

Expand comment: Roland Gruber added a comment - 2013-05-14 07:06

Roland Gruber added a comment - 2013-05-14 07:06 We already use version 1.85. Unfortunately, there is no stack trace in Jenkins log or build output. This is the build output: Started [EnvInject] - Loading node environment variables. [EnvInject] - [ERROR] - SEVERE ERROR occurs: null Finished: FAILURE We start the build by our own plugin like this: Jenkins.getInstance().getQueue().schedule(job, job.getDelay(req), parametersAction); parametersAction is a new object that only contains our own parameters. Do you depend on any values in this object?