Variables Created inside RunJob aren't Available outside Job without storing them in Bank

[BaalEvan]

Steps to Reproduce

• Create Job where you creating new Variable (for example Change "Project Name" to "Project_Name")
• Add RunJob to Main Job and call previous Job
• Add Another RunJob where variable from First Job is needed (For example FileName for Build)
• Variable isn't resolved (%VariableName% is used as FileName)

Expected Results Because there is no described way to Move Variable from One Job to Another, Variables Created inside RunJob should be available in MainJob and in all Jobs Called From MainJob

Actual Results Variable isn't Resolved and must be stored in VariableBank with RuntimeFlag

[ElmarTalibzade]

That's by design.

When you execute a Job, it generates what's called a "context". It's responsible for storing things like variables. These contexts can also reference "parent" contexts. Note that contexts don't know about "child" contexts that might reference them.

When you try to resolve a variable, RockTomate goes up that tree of contexts, starting with the current context that's accessible to it. If it can't find it in a current context, it checks the parent, then it checks its grandparent and so on until it reaches the root context (the one generated when we run the Job).

This nesting is typically created when you run Job within Jobs, creating loops or other means of nested steps.

This also means that variables created inside of Jobs that run inside another Job cannot be accessed by its parent.

Unfortunately, the workaround would be creating a variable in the root job to make it accessible.