Azure DevOps Server: Difference between revisions

Revision as of 14:52, 1 November 2022

Revision as of 21:27, 27 January 2023

Line 69:

===Clients===

Azure DevOps supports Visual Studio 2010 and later, Microsoft Test Manager (MTM) 2012, and 2013. Eclipse, older versions of Visual Studio, and other environments can be plugged into Azure DevOps using the Microsoft Source Code Control Integration Provider (MSSCCI Provider – pronounced “Miss-Key”).<ref>{{cite web

|publisher=Microsoft

|year=2012

Line 109:

==Source control==

Azure DevOps supports two different types of [[source control]] -– its original source control engine called Team Foundation Version Control (TFVC) and with the release of TFS 2013, it supports [[#Git|Git]] as a core source control repository.

===Team Foundation Version Control===

{{anchor|TFVC}}

TFVC is a centralized version control system allowing teams to store any type of artifact within its repository.<ref name="MSD-TFVC">{{cite web |title=Team Foundation Version Control (TFVC) |department=Azure DevOps |url=https://docs.microsoft.com/azure/devops/repos/tfvc/index |website=[[Microsoft Docs]] |access-date=2019-09-23}}</ref> TFVC supports two different types of workspaces when working with client tools -– Server Workspaces and Local Workspaces.<ref>{{cite web

|publisher=Phil Kelley

|year=2013

Line 172:

==Team Build==

Team Build (prior to TFS 2015) is a build server application included with Team Foundation Server. Two components make up Team Build -– [[MSBuild]] and [[Windows Workflow Foundation]]. MSBuild is a declarative XML language similar to [[Apache Ant]]. WF was added to the build process starting with TFS 2010; prior to that only MSBuild was available. The build capabilities have continued to evolve with each subsequent release of Azure DevOps. In TFS 2010 and 2012, the WF templates ([[XAML|Extensible Application Markup Language]]) files were stored in source control and could be edited and versioned directly from source control. In TFS 2013, these files were removed to eliminate clutter and streamline the build process. The WF templates can still be downloaded, edited and stored in source control if desired and TFS 2013 does not break existing TFS 2010 or 2012 build process templates. With the support of [[Git (software)|Git]] in TFS 2013, Team Build has been enhanced to allow automated building of Git projects as well as TFVC projects.

Windows Workflow controls the overall flow of the build process and Azure DevOps includes many pre-built workflow activities for managing common tasks that are performed during a build.<ref>{{cite web

Line 192:

Builds have retention policies with them so that they do not accumulate when not needed (or builds can be directed not to produce any saved output) or build output can be locked and saved forever. New with TFS 2013 is the ability to check in the build results into source control. This was a necessary enhancement to support automated builds on the Azure DevOps Services where there is no drop ___location to place the builds. In the on-premises version build output can be configured to end up in any accessible shared folder ___location.

The build process in Azure DevOps is also part of the traceability mechanism in that Team Build brings together many of the artifacts that are created and stored in Azure DevOps. Assuming developers associate source code with work items on check-in, Team Build has the ability to report on the changes in each build -– both source code changes and work item changes as well as test results (this includes [[unit testing]] results as well as automated functional testing (CodedUI) results). As bugs and [[Scrum (software development)#Product backlog|PBIs]] are resolved and integrated into builds, the work items which track these artifacts are automatically updated to indicate in which build they were successfully integrated. Combined with the testing tools, testers then get an integrated view of what code was changed in each build, but also which bugs, [[Scrum (software development)#Product backlog|PBIs]] and other work changed from build to build.

Initially, in TFS 2015 and with Visual Studio Team Services (VSTS), Microsoft has reinvented the architecture for the build engine to be based on a cross-platform friendly Node.js application. Windows, Mac, and Linux build agents are currently supported. Azure DevOps provides for elastic build capabilities via build hosting in Microsoft Azure.<ref>{{cite web