Best way to share variables between projects and libraries?

Actually the subject would be: Best way to share variables between projects and libraries? 4-inline-level calls

Lets say I have a project and 3 libraries. I need to make the following execution:

Project --> Lib A --> Lib B --> Lib C

*each "-->" represents a .runwait command in a step.

The goal is that after Lib C finish its execution and updates the variable's value, Lib B can use the updated variable, then Lib A, and finally the original caller (Project).

Right now I have to declare a variable in an environment, link every step to that environment (to have the updated value), and then edit every variable using the .set command. I would like something like .bset were I can declare variables whitout creating them, but that doesn't work (I can't see the value from Lib B)

What would be the best approach to implement this in BuildForge?

Thanks!

have you considered inlines instead of chains? (.runwait's are functionally chains)
Using inlines, you could use .bset as you describe.

Also, you shouldn't have to link every step to your env. A step inherits it's builds environment. You could set the env at the library or project level.

have you considered inlines instead of chains? (.runwait's are functionally chains)
Using inlines, you could use .bset as you describe.

Also, you shouldn't have to link every step to your env. A step inherits it's builds environment. You could set the env at the library or project level.