TFS 2010: private registration at the main branch; Rolling builds on Dev branch?

I recently moved from VSS to TFS 2010, and I was absolutely fond of it, but something still could not work as it seems to me.

GOALS

I would like to quickly find out when a change in Development breaks the assembly. If we find out about this, it does not really matter. Since there are many checks during the day, we do not want to wait for the assembly to complete, so it should be asynchronous.

In our main branch, I would like to make sure that at any time when the merger occurs, we make sure that it will not break the assembly. I need immediate feedback. The waiting time is great, as we will not merge with Main often.

CURRENT SETUP

My solution is under the Main folder. I took a break from what is called Development. The workspace in which I work is tied to the upper level, which includes both Main and Development. I tried setting up my workspace to point to Development if that was the problem. This did not seem to fix my problem, so I returned it the way I originally used it - with both Main and Development.

Within the definition of a workspace. I have two definitions defined: one for the main one and the other for development.

The first definition is for building the Main Branch. It has a Gated Check-In trigger and "Items to Build" points to the solution file in Main.

The second definition is building a solution in a development branch. He has a Rolling Builds trigger and "Items to Build" points to the solution file in Development.

RESULT

Currently, when changes are made to the development and registration is in progress, private registration in Main is launched. This not only causes confusion, but also slows down our overall process.

TRACK. STEP

I looked through some of the TFS tutorials for branching, general use of TFS, etc. Unfortunately, I have not yet found a solution to my problem. If you have encountered this problem before, I will be grateful for any suggestions you can give.

+2
source share
1 answer

At the moment, I'm not 100% sure, but the assembly should be launched using checks on parts of the source tree, which is covered by the workspace of the build definition.

Therefore, please review the assembly definition and see what part of the source tree each assembly definition receives. Your CI assembly should receive only the Dev branch, the gated assembly should have only the main branch.

+6
source

Source: https://habr.com/ru/post/1381897/


All Articles