Is there way to pass global variables through the chain?
Hello there,
I am trying to write a BuildForge project based on specific architecture, where a project is calling 2 other projects in its steps. Step 1 calling project 1, then based on the result, step 2 calling project 2.
When I try to call it inline, the main project environment variables (should I call them global) do not make to Inline called project. Meaning project1 does not know about parent project Environment.
So I did chain on success call child project and then global variables got passed to the chained project 1.
However, now I am facing another problem.
Inline project 1 run and until it is done second step of parent project is not starting, but if I do chain on pass, the child project 1 is started, but the next step in parent project does not wait for the completion, but my next step actually should wait and perform action based on result on completion of that chained project 1.
Is there way to pass global variables through the chain of the projects and make them wait for completion of each step of the chained projects?
There is a way to run project 1 and at the last step to start project 2. However it is not desirable behavior.
Thanks in advanced,
Alex K
I am trying to write a BuildForge project based on specific architecture, where a project is calling 2 other projects in its steps. Step 1 calling project 1, then based on the result, step 2 calling project 2.
When I try to call it inline, the main project environment variables (should I call them global) do not make to Inline called project. Meaning project1 does not know about parent project Environment.
So I did chain on success call child project and then global variables got passed to the chained project 1.
However, now I am facing another problem.
Inline project 1 run and until it is done second step of parent project is not starting, but if I do chain on pass, the child project 1 is started, but the next step in parent project does not wait for the completion, but my next step actually should wait and perform action based on result on completion of that chained project 1.
Is there way to pass global variables through the chain of the projects and make them wait for completion of each step of the chained projects?
There is a way to run project 1 and at the last step to start project 2. However it is not desirable behavior.
Thanks in advanced,
Alex K
3 answers
Hello there,
I am trying to write a BuildForge project based on specific architecture, where a project is calling 2 other projects in its steps. Step 1 calling project 1, then based on the result, step 2 calling project 2.
When I try to call it inline, the main project environment variables (should I call them global) do not make to Inline called project. Meaning project1 does not know about parent project Environment.
So I did chain on success call child project and then global variables got passed to the chained project 1.
However, now I am facing another problem.
Inline project 1 run and until it is done second step of parent project is not starting, but if I do chain on pass, the child project 1 is started, but the next step in parent project does not wait for the completion, but my next step actually should wait and perform action based on result on completion of that chained project 1.
Is there way to pass global variables through the chain of the projects and make them wait for completion of each step of the chained projects?
There is a way to run project 1 and at the last step to start project 2. However it is not desirable behavior.
Thanks in advanced,
Alex K
There is wait pass and wait fail for the chain projects. That resolves this issue. Thank you for reading anywan.
Alex K.
I would do it with a .runwait command. This behaves the same as a chain (or a .run) except that it waits for the completion of the child project before continuing execution in the parent.
You could also accomplish the same thing by turrning on "pass wait" on the chaining step. It has the same effect of causing the step to wait for it's child's completion.
You could also accomplish the same thing by turrning on "pass wait" on the chaining step. It has the same effect of causing the step to wait for it's child's completion.
I would do it with a .runwait command. This behaves the same as a chain (or a .run) except that it waits for the completion of the child project before continuing execution in the parent.
You could also accomplish the same thing by turrning on "pass wait" on the chaining step. It has the same effect of causing the step to wait for it's child's completion.
Thank you rhaig, I just figured it out few minutes ago.
Alex K