You need to enable JavaScript to run this app.
优惠活动
大模型
产品
解决方案
定价
更多

咨询TFS2017中XAML定义的CI逐签入构建在VNext中的等效设置

Great question! Let's break this down clearly for TFS 2017 (version 15.117.27414.0):

XAML vs. VNext Build Trigger Equivalents

First, let's clarify the mapping between your old XAML setting and VNext triggers:

  • The XAML definition's "Continuous Integration - build each check-in" directly maps to the standard Continuous Integration (CI) trigger in VNext (not the Gated trigger's supplementary option).
    • If you uncheck batch changes in the CI trigger settings, that's the exact 1:1 match—it runs a build for every individual check-in. Enabling batch changes groups multiple check-ins into a single build, which is a variation, not the equivalent of "build each check-in".
Why Your CI Build Isn't Triggering After Gated Check-in

The issue you're facing (no CI build firing post-successful Gated check-in) is tied to how TFS 2017 handles these triggers by default:

  • Out of the box, TFS assumes the Gated Check-in build already validated your changes, so it won't automatically fire a separate CI build for the same committed changes.
  • The "Run continuous integration triggers for committed changes" option in the Gated trigger is exactly the fix here. This setting overrides the default behavior, telling TFS to kick off your CI build (with its unique steps) even after a successful gated check-in.
Recap of Your Original Questions
  1. No, the Gated trigger's "Run continuous integration triggers for committed changes" is not the equivalent of the XAML CI setting—it's a supplementary toggle to enable CI runs after gated check-ins.
  2. The standard CI trigger (with batch changes unchecked) is the direct equivalent of XAML's "build each check-in".
Step-by-Step Fix to Trigger CI After Gated Check-in

To get your CI build to run post-gated check-in:

  1. Open your Gated Check-in build definition.
  2. Navigate to the Triggers tab.
  3. Under the Gated trigger configuration, check the box for "Run continuous integration triggers for committed changes".
  4. Save the gated build definition.

Now, every time a gated check-in completes successfully, TFS will trigger your separate CI build with the committed changes—perfect for your scenario where the two builds have different steps.

内容的提问来源于stack exchange,提问作者Felipe

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.05.28 09:21:59