On Thu, 23 Apr 2015 15:08:49 +0200, Rafael Ribeiro Rezende
<[email protected]> wrote:
So, I would like a hint here. Is it failing because something in the
EnvInject itself got broken some time ago? Or the build server changed
its
configuration somehow?
As I am looking at it, this is caused by JENKINS-26583[1] - envinject
captures variable value early and do not overwrite it. The reason this
manifests when tests are run from Jenkins is the WORKSPACE variables is
set during build but it likely is not on your development box. I have just
reproduced the failure locally running `WORKSPACE=XXX mvn clean package
-Dtest=EnvInjectBuildWrapperTest#testPropertiesContentCustomWorkspace`.
I gave up[2] half way trying to untangle countless variable contribution
sources in the plugin.
[1] https://issues.jenkins-ci.org/browse/JENKINS-26583
[2] https://github.com/jenkinsci/envinject-plugin/pull/37
--
oliver
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/op.xxs7gywisbfict%40arch.
For more options, visit https://groups.google.com/d/optout.
