Vsts构建定义 - 防止PowerShell退出行为导致进程终止(VSTS build definition - prevent PowerShell exit behavior causing processes termination)

 所以我在我的定义中有一个PS任务，它自己调用另一个脚本文件，负责在我的构建代理上运行几个东西（启动几个不同的进程） - 模拟器， node.js应用程序等。一切都很好，直到这一步完成并继续运行。 所发生的是所有上述内容都被关闭，大多数底​​层进程被杀死，因此，任何进一步的执行（例如测试运行）都注定要失败。 
 
 我的假设是这些进程以某种方式依赖于VSTS生成的最外层（临时）脚本来处理该步骤。 我尝试使用我的脚本的参数列表中指定的-NoExit开关，但无济于事。 我还在某处读到了一个建议，默认情况下使用powershell.exe的注册表项设置它 - 仍然没有。 
 
 在詹金斯，同样的工作流程也没问题。 所以我想知道是否有人经历过这个并且可以提供帮助？ 先谢谢你。 
 
 编辑 
 
 所以这些是我的任务： VSTS任务 
 
 最后一个PowerShell任务调用指定的PS文件，该文件自己调用其他几个文件。 它们确保了开始执行测试所需的一些本地依赖项和进程，例如运行的node.js应用程序（例如，在单独的控制台中启动并运行正常）。 当任务完成并且成功时，带有测试的最后一个将失败，因为node.js应用程序已关闭，以及在上一步骤中启动的任何其他应用程序。 它只是阻止一切。 这就是为什么我目前正在同一个任务中运行测试，直到我找到如何克服这种行为。 

I have a PowerShell task in my definition that calls another script file on its own which takes care of running several things on my build agent (starts several different processes) - emulators, node.js applications, etc. 
 
Everything is fine up until the moment this step is done and the run continues. All of the above mentioned stuff gets closed with most of the underlying processes killed, thus, any further execution (e.g. tests run) is doomed to fail.
 
My assumption is that these processes are somehow dependent on the outermost (temporary) script that VSTS generates to process the step.
 
I tried with the -NoExit switch specified in the arguments list of my script, but to no avail. I've also read somewhere a suggestion to set this by default with a registry key for powershell.exe - still nothing.
 
The very same workflow was okay in Jenkins. How can I fix this?
 
These are the tasks I have:
 
 
The last PowerShell task calls a specified PowerShell file which calls several others on its own. They ensure some local dependencies and processes needed to start executing the tests, e.g. a running Node.js application (started in a separate console for example and running fine).
 
When the task is done and it is successful, the last one with the tests would fail because the Node.js application has been shut down as well as anything else that was started within the previous step. It just stops everything. That's why I'm currently running the tests within the same task itself until I find out how to overcome this behavior.

原文：https://stackoverflow.com/questions/43203959