"${WORKSPACE}" was a poor example ... how about "${SOME_RANDOM_FOLDER}" ..
the point was, when param goes to get passed, it doesn't evaluate any
nested parameters, just passes it straight text.
On 19 September 2014 00:46, Jan Seidel <wakkal...@gmail.com> wrote:
> ${WORKSPACE} is dynamic.
> Job A and job B have their own defined workspace and will use different
> values.
> If you want job B to use the same you could pass the value as parameter
> like:
>
> ALT_WORKSPACE=${WORKSPACE}
>
>
> Am Dienstag, 16. September 2014 03:21:03 UTC+2 schrieb Brantone:
>>
>> 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 a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/xgx3snzEgsI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
