vNext中的批处理脚本任务未正确报告结果 [英] Batch script task from vNext is not reported result correctly
问题描述
大家好,
我的批处理脚本任务是从vNext build,TFS 2015.2调用signtool.exe来签署二进制文件。报告vNext构建此批处理脚本已成功运行,如下面的屏幕截图;但是,当我检查文件时,它没有签名。
我在构建服务器上手动运行此批处理脚本。它运行成功,文件已签名更正。我使用与运行代理服务相同的用户远程登录构建服务器。我错过了什么吗?请指教。
I've batch script task which is invoking signtool.exe to signing binary files from vNext build, TFS 2015.2. vNext build is reported this batch script has run successful as screen capture below; however, when I check the file, it is not signed. I run this batch script manually on build server. It runs successful and file is signed corrected. I remote login to build server with the same user as running agent service. Am I missing something? Please advise.
最诚挚的问候,
Andy Pham
Andy Pham
最诚挚的问候,Andy Pham
Best Regards, Andy Pham
推荐答案
嗨Andy,
感谢您在此发帖。
根据您的说法描述批处理文件可以在构建服务器上本地执行。因此,您可以尝试在本地运行签名脚本。试试下面的事情:
According to your description the batch file can be executed locally on the build server. So you can try to run the sign script locally. Just try below things:
- 将批处理脚本转移到PowerShell 脚本,
- 将批处理文件复制到远程构建服务器,
- 在构建定义中添加 PowerShell on Target Machine 任务(部署任务),并指定正确的参数。
- Transfer the batch script to PowerShell script,
- Copy the batch file to the remote build server,
- Add a PowerShell on Target Machine task (Deploy task) in build definition, and specify the correct parameters.
对新版本进行排队以检查结果。
Queue a new build to check the result.
最好的问候。
这篇关于vNext中的批处理脚本任务未正确报告结果的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!