[
https://issues.jenkins-ci.org/browse/JENKINS-13647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162711#comment-162711
]
Gregory Boissinot commented on JENKINS-13647:
---------------------------------------------
Fixed.
The error was not due to the EnvInject plugin.
EnvInject plugin only participates to have an isolate build by managing
environment variables.
The Batch-Task plugin delegates environment variables to the EnvInject library.
The library is embedded in the batch-task plugin distribution (the installation
of the EnvInject plugin is not required).
EnvInject library calls programmatically all build actions. In your use case,
these actions contained an action from the rebuild plugin.
And RebuildAction object threw an exception when the project object can't be
retrieve from the request (the use case in the batch-task plugin context).
I fixed it in the rebuild plugin.
Please upgrade to rebuild plugin 1.11.
> Environment variables from EnvInject plugin are not inherited/parsed by batch
> tasks
> -----------------------------------------------------------------------------------
>
> Key: JENKINS-13647
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13647
> Project: Jenkins
> Issue Type: Bug
> Components: batch-task
> Affects Versions: current
> Reporter: tsondergaard
> Assignee: Kohsuke Kawaguchi
> Attachments: config.xml
>
>
> Environment variables set for a job with the "Prepare an environment for the
> run" and not processed/used for batch tasks. This is very similar to bug
> JENKINS-5580 reported for batch tasks and the now deprecated setenv plugin
--
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
