Build lab

A lab or a VBL (virtual build lab) commonly refers to a team working on a part of the Windows operating system, or the source code branch that the team works on. Originally, a build lab was a room with machines periodically producing official builds of Windows NT. Initially, there was a single build lab for the entire project, however, as the number of developers grew, teams working on different parts of the operating system were assigned their own virtual build labs, which included a branch of the project code, as well as the infrastructure to build the code. This carried over to Source Depot branch names, which led to the term being also used for the teams themselves and the branches.

Builds that were not built by the build lab machines are called private builds. They are identified by having the VS_FF_PRIVATEBUILD file flag set in the executable's version information and by including the account name of the person or service who initiated the build in the branch part of the build tag.[note 1]

Labs[edit | edit source]

Microsoft has used several branching systems since the start of Windows XP development, which differ in the hierarchy of labs as well as in the naming scheme. However, there are some specifics common to most schemes, such as the presence of a top-most main branch, or the use of special branches for important development milestones.

Whistler and pre-reset Longhorn[edit | edit source]

The top-most branch (sometimes called the "trunk") was called main, which integrated changes from all labs. Under it were several numbered labs, each of which was working on a separate part of Windows, such as:

  • Lab01: Kernel
  • Lab02: Networking
  • Lab03: Server[note 2]
  • Lab04: Terminal Services[1]
  • Lab06: User interface
  • Lab07: Internet Information Services/COM+ (added in Longhorn)

These labs also had a "_N" branch, which served as a buffer between main and the actual branch. For example, changes from main would first get integrated into Lab06_N before later being integrated into Lab06 in a process called forward integration. The same applied for reverse integration, where the lab would first integrate changes into its N-branch before integrating them into main.

Before the labs were actually named "Lab0_", they were introduced in Windows XP development as ntvbl0_. However, the only build to be built by such a lab is build 2202 and so far the only lab which compiled such a build was "ntvbl06" as a few months later, the labs have been renamed to "Lab0_".

There were also idx (internal development workstation/server) branches, builds from which are usually recompilations intended for TAP/OEM partners. However, they were also occasionally released for public testing, e.g. Windows Longhorn build 4074 or Windows XP build 2257.

Before the release of Windows XP, the trunk was forked into the xpclient branch while the main branch moved on to track Windows Server 2003 development. After the final version was shipped, new branches such as xpsp were created for updates, hotfixes and Service Pack development. Similarly, the dnsrv branch was forked from the trunk before the release of Windows Server 2003. Shortly before its release, the branch was renamed to srv03. However, the dnsrv branch name was still used for Service Pack pre-releases as well as Windows Server 2003 R2, which even shipped as RTM with dnsrv in its build tag.

Since Longhorn reset[edit | edit source]

The lab hierarchy was overhauled after the development reset of Longhorn to address the flaws that plagued most of the pre-reset period. Instead of having a small amount of general virtual build labs each focusing on a different general scope of Windows functionality, a new hierarchic model with considerably more feature branches has been introduced, which helped reduce the amount of code to reverse integrate for branch. Microsoft also set stricter criteria for reverse integrating changes from the labs into the trunk, which was now renamed to winmain.

The trunk branch was renamed to rsmaster at some point after the Windows source repository has been converted to Git, possibly to comply with the Git convention of calling the top-most branch the master branch.

Feature branch prefix[edit | edit source]

Microsoft has used multiple prefixes to refer to feature branches over time:

Windows 10 November Update and Windows 10 Anniversary Update used their release branch prefix for feature branches.

Release branch prefix[edit | edit source]

Similarly to the previous system, the main branch is forked off before release to contain update development. The following is the list of known prefixes:

Notes[edit | edit source]

  1. For example, build 6.0.4067.private/lddm_dev_tech(davidmo).040212-1646 is a private build initiated by the davidmo user.
  2. This lab compiled client builds even though it worked on server components, because the build process does not distinguish between SKUs.

References[edit | edit source]

External links[edit | edit source]