Change By: Lars Francke (10/Apr/13 8:55 AM)
Description: JENKINS-15962 broke this functionality with this [commit|https://github.com/jenkinsci/config-file-provider-plugin/commit/05f431815f32d7ce5e74d661791b4a08313b20ed].

We are using an environment variable set by this plugin in the Maven command line. Ever since that commit these variables are not set anymore.

The problem is that {{ConfigFileBuildWrapper}} doesn't return an {{Environment}} anymore but registers an action instead which then in turn should register the environment variables. Unfortunately {{MavenModuleSetBuild}} only takes the returned {{Environments}} from {{BuildWrapper}}
s   into account but not those from actions registered by them.

I can fix this by reverting part of the commit mentioned above. This is the first time I've ever dug into Jenkins' code so there might be a simpler solution or this might even be a bug in Jenkins itself. I'm not sure.

I'll attach this simplistic patch but I'm happy to try to work on a better one if given instructions.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to