For anyone wondering, I can't remember where I read it, but it doesn't
evaluate it unless you pass it as predefined.
When using "current build parameters" it just does it exactly as is, as if
it was typed in that way.
The mention/verification was in a random comment somewhere, just can't find
it.
Anyway, thread closed.
On Monday, 15 September 2014 18:21:03 UTC-7, Brantone wrote:
>
> Perhaps just not using the right terms to look for an answer as I'm
> thinking this isn't crazy unique.
>
> So "Job A" triggers "Job B".
>
> Job A has a parameter called PROJECT_PATH, whose value =
> "${WORKSPACE}/project/trunk/".
>
> When triggering Job B choosing "Current Build Parameters", It passes it
> straight as is, but I want it to expand on "${WORKSPACE}" so it actually
> uses the value from Job A.
>
> Something simple I'm missing??
>
--
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].
For more options, visit https://groups.google.com/d/optout.
