h it represents a security
> breach
>
>
>
> *From:* jenkins...@googlegroups.com [mailto:
> jenkins...@googlegroups.com ] *On Behalf Of *Daniel Hiller
> *Sent:* 12 May 2016 16:28
> *To:* Jenkins Users
> *Subject:* Re: $MVN_RELEASE_VERSION missing after Upgrade to Je
One more thing I forgot: I'm using this env var in an "Execute Shell" Post
Step, where it is read from within the executed script, perhaps that's the
problem?
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: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Daniel Hiller
Sent: 12 May 2016 16:28
To: Jenkins Users
Subject: Re: $MVN_RELEASE_VERSION missing after Upgrade to Jenkins 2
Hi again,
just found this JIRA issue: https://issues.jenkins-ci.org/browse
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
