[
https://issues.jenkins-ci.org/browse/JENKINS-13647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162678#comment-162678
]
jcarsique commented on JENKINS-13647:
-------------------------------------
Well, I don't know since downgrading batch-task is fixing the issue, even if
it's the rebuild-plugin which throws the exception. I'm not sure to understand
why the rebuild-plugin is called when executing a batch task, but if it was
already called before that change, then its "current project" wasn't null...
Do you think the use of EnvInject in batch-task requires some upgrade on
rebuild-plugin? Isn't there a broken backward compatibility which could be
fixed in EnvInject?
> 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
