How can I prevent the binding of TFS work items to the assembly?

Question

I am trying to set up automatic notifications for our test group so that they say when they are ready to check user history.

Notifications are currently triggered when the "Fixed in" assembly for a work item changes.

Our nightly build is deployed on an intermediate server. I want this assembly to update the "Fixed" assembly.

In addition, we have a gated line. I do not want this to update the "Fixed In" assembly.

I tried to change the "Associate Changesets and Work Items" property in the assembly definition to "false", but the private check is still related to (and updating the "Fixed in" work items).

How can I prevent my gated checkin from being associated with work items?

Is there another smarter way to automatically notify a test group when a work item is ready for testing (as opposed to being tested)?

Answer 1

We have a similar setup when we run 'private', when developers register in the DEV branch and the "integration" assemblies, which are actually the ones that belong to the test team.

Both 'private' and 'integration' assemblies are made from the same assembly process template, but are different build definitions.

We built the user activity "Types.cs" in the build solution (basically a simple enumeration):

namespace BuildTasks.Activities { public enum QATypes { Private, Integration, Release } } 

This is conveyed as the possible values ​​of the build argument we added with the name "BuildType":
.

This now appears as a custom assembly definition parameter:

We obviously introduce 'private' or 'Integration' in each definition, respectively. At the final stages of our process, we check the value of this parameter and, depending on it, we send (or not) a letter to the QA alias.

You may be able to organize a similar implementation to meet your needs.