Azure DevOps文件转换任务，而不是遇到转换问题的问题
我们有一些发行管道可以执行Web.config对他们将要使用DevOps Marketplace的文件转换任务的环境进行转换。我们从另一个团队继承了这个项目，99％的时间在此设置中没有任何问题。但是，上周，我们为该项目进行了发行版，并且生产配置未正确转换，并且当更新进行生产时，它已配置为连接到我们的开发环境环境设置。
查看发行版的日志，文件转换任务完成了绿色，但有一个警告：
2022-04-19T21:38:13.2301719Z ##[warning]Unable to apply transformation for the given package.
希望看到该任务失败并给我们一个警报，以便我们可以审查该问题并将版本的其他部分回滚，其中包括API更新和数据库更新，但不确定如何执行此操作。是否有任何方法可以将上述警告视为该任务的失败？
We have a few of our Release pipelines that perform the web.config transforms for the environment they are going to using the File Transform task from the DevOps marketplace. We inherited this project from another team, and 99% of the time no issues have come up with this setup. However, last week we performed a release for this project to production and the Production config did not correctly transform and when the update went to production it was configured to connect to our dev environment settings.
Looking at the log of the release, the File Transform task finished green but had a single warning:
2022-04-19T21:38:13.2301719Z ##[warning]Unable to apply transformation for the given package.
Would like to have seen the task fail and given us an alert so that we could have reviewed the issue and rolled back the other bits of the release, which included an API update and Database update, but not sure how to do that. Is there any way to have that warning listed above be considered a failure for the task?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
同意。我认为MS在过去几天中已经打破了这一点。
似乎有效的转换任务有一个版本2（预览）。我建议在MS排序之前使用它。
Agreed. I think MS have broken this in the last couple of days.
There is a version 2 (preview) of the transform task that seems to work. I suggest using that until MS sort it.