隔夜破坏VSTS的变化 [英] Breaking changes on VSTS overnight

问题描述

我们在VSTS过夜（5月4日 - > 2016年5月5日）运行的版本中经历了许多重大变化。其中包括：

- 'npm'构建步骤用于在'command'输入中允许多个空格分隔的命令（例如，对于`npm run linter`），但现在需要'command'中的单个命令以及'arguments'中的任何内容。我同意这现在更有意义，但是
此更改打破了我们的所有构建，并要求我们返回并更改多个构建步骤以匹配新行为。

- The 'npm' build step used to allow multiple space-separated commands in the 'command' input (e.g. for `npm run linter`), but now requires a single command in the 'command' and anything further in 'arguments'. I agree that this now makes more sense, however this change broke all of our builds, and required us to go back and change multiple build steps to match the new behaviour.

- 向GitHub报告提交触发的构建的CI服务名称已更改。这意味着，如果我们为"受保护的分支机构"设置了规则，只允许在VSTS上进行测试时合并拉取请求，我们必须更改那些
规则以匹配新名称。

- The CI Service name reported back to GitHub for commit-triggered builds has changed. This means that where we had rules set up for 'protected branches' to only allow pull requests to be merged if tests on VSTS had passed, we had to go and change those rules to match the new name.

我完全理解有时需要进行重大更改，但有人可能会指向我指向博客/发布说明/新闻项目的方向变化将会发生？在没有事先（或追溯！）通知用户的情况下进行这些类型的b $ b变更是不可接受的，而且我还没有找到任何升级的提及。

I totally appreciate that sometimes breaking changes are necessary, however could someone point me in the direction of a blog/release notes/news item that indicated that these changes were going to happen? It's not acceptable for these sorts of changes to be made with no prior (or retrospective!) notice to users, and as yet I've not been able to find any mention of upgrades being made.

推荐答案

我一直在寻找一个即将发生变化的地方。获得概述会很好，因为我们已经通过更新任务解决了很多解决方法。

I have also been looking for a place where the upcoming changes are detailed. It would be nice to get the overview as we have a lot of workarounds in place that have been resolved by an update to the tasks.

有服务博客，但更多的是问题/停工时间而非发布。

There is the service blog, but that is more about issues/downtime than releases.

这篇关于隔夜破坏VSTS的变化的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！