Yeah, that's what I was hoping to avoid. Simply choosing "Use Current Parameters", and have it auto-magically include the evaluated value ... which is not feasible, so I'm trying to do something it's not meant to do. Hence, thread closed ;)
On 19 September 2014 02:13, Jan Seidel <[email protected]> wrote: > > <https://lh4.googleusercontent.com/-4T5_n-5GX-g/VBvzo1dJLlI/AAAAAAAACjA/ALPF_Bn5QoI/s1600/Untitled.png> > Ah, I got your point :) > use the "Predefined parameters" opton. Then the variables will expand. > See picture attached > > 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 > [email protected]. > 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
