Rebuilding only the changed environment (instead of all of them)

[sesame0707]

Hello!

Is there an option to exclude all the other environments from rebuilding when working on a given environment? In other words, when I'm making changes to only one environment and the rebuild is triggered, then all of my environments are being rebuilt (which takes about 9 minutes in my case) instead of rebuilding only the changed one. Is there any way to change this behavior to rebuild only the changed one instead?

[Den1552]

Hi @sesame0707,

If you have a single environment (not embedded in a project), you can right-click on the environment node → VectorCAST → Re-Build Environment.

If you are working with projects, you can either rebuild individual environments in the same way, or you can right-click on the project, compiler, or testsuite node and select VectorCAST → Build/Execute Incremental. This will rebuild all environments hierarchically beneath that node and re-execute all tests.

[sesame0707]

Thank you for the answer, but unfortunately that's not the case I was thinking of.

Hence, let me rephrase my question: Sometimes (probably when I modify something within my Project (e.g., the "XYZ" Environment) from within the VectorCAST GUI), when I switch back to VS Code, all the Environments from my Project start to rebuild (which takes about 9 minutes to complete in my case). Is there a way to block all the other Environments except for the "XYZ" Environment from being rebuilt?

I'm aware of that my question is not precise, because I myself don't know what exactly triggers the Environments from within VS Code to rebuild. I'll be on the lookout for this behavior in the future, and hopefully will catch the root cause

[sesame0707]

For example, when you open up VS Code "from scratch", all the environments are being rebuilt - that's one of those triggers

[aytey]

@sesame0707 we think this might be a bug; we converted this to #268 -- could you reply there?

[sesame0707]

Sure 👍