Azure批处理:是否不再在本地节点上创建ProcessEnv.cmd? [英] Azure Batch: Is ProcessEnv.cmd not created on the local nodes anymore?

问题描述

我们复制了ProcessEnv.cmd，stderr.txt和stdout.txt进行错误检查.几周前，我们停止获取ProcessEnv.cmd.

We copy over ProcessEnv.cmd, stderr.txt, and stdout.txt for error checking. We stopped getting ProcessEnv.cmd a few weeks ago.

这是否由于某种原因而消失了?如果是这样，我们在哪里可以找到Azure Batch发生的类似变化.

Did this go away for some reason? And if so, where do we find out about changes like this that happen to Azure Batch.

PS.现在，我们将其包含在我们的任务中，以创建自己的ProcessEnv.txt: SET> ProcessEnv.txt

PS. We now make our own ProcessEnv.txt by including this in our task: SET>ProcessEnv.txt

谢谢

斯科特

推荐答案

斯科特，你好，

Hi Scott,

ProcessEnv.cmd是一个未记录的文件，被创建为内部实现的详细信息.任务不应该依赖此文件，因为永远不能保证文件的存在.

ProcessEnv.cmd was an undocumented file that was created as an internal implementation detail. Tasks should not be taking a dependency on this file as its existence was never guaranteed.

更改与以下内容有关: https://github.com/Azure/Batch/issues/1

The change is related to: https://github.com/Azure/Batch/issues/1

GitHub存储库是一个很好的资源，可以随时了解公告和对节点代理的更改.

The GitHub repository is a good resource to keep up to date on announcements and changes to the node agent.

干杯

弗雷德

这篇关于Azure批处理:是否不再在本地节点上创建ProcessEnv.cmd?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！