The easiest way to test the TFS2010 build template

Question

I am currently working on creating an assembly template for the TFS2010 assembly. However, I notice that I am currently “spamming” using the source control with every change I make in the template (and much more for all the fixes for these changes).

Interestingly, the easiest way to check the assembly templates that I create? Is there a way to modify template files and custom DLLs that do not include checking them?

Currently, I have a build controller and agent running on my developer's machine, which I use to test the template (test = start building and hope for fewer errors than last time).

Answer 1

Why is "spamming" a problem? In any case, I have a separate Team Project to carry out such work, so I can register in my heart without affecting developers who need a stable build. as soon as I have finished testing, I check the template in the project (s), which is used by the developers.

Answer 2

I want to test my builds against the latest command code base without passing it to a test project.

Instead, I do the following:

• Create a separate assembly definition called Infrastructure
  • clone production definition
• Define a trigger to determine infrastructure construction in the manual.
• Set infrastructure definition permissions to allow only members of the [Project] \ Build group to have full control over it.
  • saves notification of broken lines from the main part of the command).
• Create a separate build process template called .xaml Infrastructure.
• Specify the infrastructure assembly definition in the infrastructure process template.

Now that I want to repeat the new build function for the command:

• Check the build process template I want to update and lock it.
• Copy the assembly process template. I want to update the top panel of Infrastructure.xaml.
• Add my build function to the Infrastructure.xaml file and check it out.
• Use the infrastructure assembly definition to verify my changes.
• Go through 3-4 until I get it right.
• Fill this feature and change my changes with another member of the infrastructure team.
• Copy Infrastructure.xaml according to the template of the build process. I blocked (1) and checked it.

This still leads to spam in the TFS source control, but it keeps the iteration of the assembly definition in the eyes of the team. Build process templates come from the main source tree (in the Build Process Templates folder or in the branches themselves in the Core / Build folder, where no one in the team usually pays attention) so that the team is not significantly affected by it.

Answer 3

@ d3r3kk: Why not just expand the template and merge the changes when they are ready, and not create copies? That way you can also keep the original story in a cleaner way.

Ideally, there should be a way to create a template for the assembly process located in its local file system and temporarily indicate the definition of the assembly. Not sure if there is something similar in later versions of VS / TFS. I still did not see it accessible through the interface.