[
https://issues.jenkins-ci.org/browse/JENKINS-13647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162658#comment-162658
]
Gregory Boissinot edited comment on JENKINS-13647 at 5/10/12 7:51 PM:
----------------------------------------------------------------------
According to the trace, it is due to the rebuild Jenkins Plugin
{code}
AbstractProject currentProject = null;
StaplerRequest request = Stapler.getCurrentRequest();
if (request != null) {
currentProject = request.findAncestorObject(AbstractProject.class);
}
if (currentProject == null) {
throw new NullPointerException("Current Project is null");
}
{code}
was (Author: gbois):
According to the trace, it is due to the rebuild Jenkins Plugin
{code}
AbstractProject currentProject = null;
StaplerRequest request = Stapler.getCurrentRequest();
if (request != null) {
currentProject = request.findAncestorObject(AbstractProject.class);
}
if (currentProject == null) {
throw new NullPointerException("Current Project is null");
}
{code}
> 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
