跨不同Team Project执行Build与Release时Commits标签异常问题

Hey there, let's break down what's happening here and how to work around it.

First off: this isn't a bug—it's a known design limitation (you could call it a "feature" rooted in older project boundary rules) in TFS 2017's Release Management when working across team projects.

Why this error pops up #

TFS 2017's Release system, when loading the Commits tab, only searches for build definitions within the same team project as the release pipeline itself. So when your releases project's pipeline pulls artifacts from proj1's build definition, it tries to look up that build ID inside releases (where it doesn't exist) instead of checking the proj1 project. That's exactly why you get the "build definition XXX was not found" message.

Practical workarounds you can use right now #

Here are a few options depending on your team's needs:

• Mirror the build definition in the releases project
  Export the build definition from proj1, import it into releases, and update your release pipeline to use this mirrored copy. This works, but keep in mind you'll have to maintain two versions of the build config if you make changes later. Ideal for stable build processes that don't get updated often.

• Navigate directly to the source build
  The simplest fix: just jump to the proj1 team project, find the specific build linked to your release, and view the commits directly there. No extra setup needed—just a quick navigation hop.

• Upgrade to a newer Azure DevOps Server version
  Microsoft fixed this cross-project dependency lookup issue starting with TFS 2018 (and all subsequent Azure DevOps Server releases). If your team has the bandwidth to upgrade, this is the permanent solution—you'll no longer hit this error, and the Commits tab will work seamlessly across projects.

• Build a custom dashboard widget
  If you need to view commits directly in the releases project, you can create a custom dashboard widget using the TFS REST API. The widget would pull commit data from the proj1 build and display it in your releases dashboard. Note this requires some basic development work to set up.

Quick context #

This limitation stems from how TFS 2017 enforced project boundaries—back then, cross-project resource access was more restricted. Later versions relaxed these constraints to better support centralized release management workflows like yours.

内容的提问来源于stack exchange，提问作者Erez H