Hi again, just found this JIRA issue: https://issues.jenkins-ci.org/browse/JENKINS-12128
There it is clearly stated that these variables are exposed. Now I don't understand what I have to change to be able to access them again? Regards, Daniel Am Donnerstag, 12. Mai 2016 17:21:48 UTC+2 schrieb Daniel Hiller: > > Hi all, > > I've made the step to upgrading our jenkins server from 1632 to > 2.3.whatever (hooray!) and everything seems to work fine except one thing: > > looks like environment variable $MVN_RELEASE_VERSION is not set during the > build when using the M2 release plugin. I don't know how or why it was set > (didn't find any documentation about that) but what I know is that it used > to work in 1.632 (we relied on this magic setting where we found the > release version number) > > Now I don't want it back, I just want to know who was responsible for > setting it and how I can re-set this variable so that everything will work > again. Can anybody shed sone light on this here please? > > Thanks for your time, > > Daniel > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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-users/9a5aefbf-a040-4f8d-9c3c-855f89bc6ff1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
