Hey, is this issue resolved ? I have exactly the same issue , I have to pass few variables to child plan. Is the any correct way to do it? or any workaround to override the variables in script. Any help is appreciated

Wow this is an old issue but I have now run into a scenario where this is needed.

use case: I have a task that I'd like to run on ALL plans, think of it as a shared task, but each plan would need to pass in some variables at runtime. 

Issues I see

• I can trigger a child plan but can not share an artifact from more then 1 parent plan
• I can use the inject functionality on the parent plan, but there is no way to pass them to the child plan when it's triggered
• I can manually trigger all these steps individually but can not automate them
• I can move the task from the child plan to the parent, but if I need to update the task, I have hundreds of plans/tasks that I would need to now update

Solution: create a plan/task that can be shared on all parent plans and have the ability to pass variables from the parent plan to the child plan, when called

Any progress on this?

I have two plans, one for deploying and one for running tests. Both can be configured with variables to be executed for specific environment. However, it is useless if I can't trigger my test plan to be built with specific variable that matches the environment services were deployed to.

If I can run plan customized manually, why can't I do it automatically?

@James Dumay has this been implemented? - Surely it's close? 

will this be implemented in near future.

Any idea of when this is going to be implemented

Good to know, my apologies. I was led astray.

While you may not approve of the workaround (I personally would like the metadata to expose more than just the build that triggered the child without having to REST it up), using a variable file artifact on the parent, an artifact download on the child, and the inject variables task absolutely works on remote agents.

This is not an acceptable workaround, as it is incompatible with the use of remote agents

To work around this, parent plan can dump variables into a file which can be shared as an artifact to child plan. In child plan, download the shared artifact inject this variables in the child plan.