Azure DevOps Server: Difference between revisions

Browse history interactively

← Previous edit

Content deleted Content added

VisualWikitext

Revision as of 11:36, 15 February 2021 edit 178.38.169.177 (talk) →History: anchor part of link corrected ← Previous edit		Latest revision as of 09:50, 26 July 2025 edit undo 203.145.89.5 (talk) article not exist
(37 intermediate revisions by 33 users not shown)
Line 1: {{short description\|Source code management software}} ~~{{Multiple issues\|~~ ~~{{self-published\|date=May 2014}}~~ ~~{{third-party\|date=May 2014}}~~ }} {{Infobox software \| name = Azure DevOps Server Line 12 ⟶ 8: \| developer = [[Microsoft]] \| released = {{Start date and age\|2005}} \| latest release version = ~~2019 Update 1 Patch 1~~2022 \| latest release date = {{Start date and age\|~~2019~~2022\|0912\|1006}}<ref>{{cite web \|title=Azure DevOps Server ~~2019 Update 1 Release Notes~~2022 \|url=https://~~docs~~learn.microsoft.com/fr-fr/azure/devops/server/release-notes/~~azuredevops2019u1~~ azuredevops2022?view=azure-devops\|website=[[Microsoft Docs]]\| ~~\|access-~~date=~~2019-10-12~~14 November 2023 }}</ref> \| operating system = [[Microsoft Windows]] \| language = Line 20 ⟶ 16: }} '''Azure DevOps Server''', (formerly known as '''Team Foundation Server''' ('''TFS''') and '''Visual Studio Team System''' ('''VSTS''')), is a [[Microsoft]] product that provides [[version control]] (either with [[#TFVC\|Team Foundation Version Control]] (TFVC) or [[Git (software)\|Git]]), reporting, [[requirements management]], [[project management]] (for both [[agile software development]] and [[waterfall model\|waterfall team]]s), automated builds, [[software testing\|testing]] and [[release management]] capabilities. It covers the entire [[Application Lifecycle Management\|application lifecycle]], and enables [[DevOps]] capabilities.<ref>{{cite web \|url=http://msdn.microsoft.com/en-us/library/vstudio/fda2bad5(v=vs.120).aspx \|title=Application Lifecycle Management with Visual Studio and Team Foundation Server \|year=2013 \|website=[[Microsoft Developer Network\|MSDN]] \|publisher=Microsoft \|access-date=2013-10-15}}</ref> Azure DevOps can be used as a back-end to numerous [[integrated development environment]]s (IDEs) but is tailored for [[Microsoft Visual Studio]] and [[Eclipse (software)\|Eclipse]] on all platforms.<ref>{{cite web \|url=http://msdn.microsoft.com/en-us/library/gg413285.aspx \|title=Adopting Team Explorer Everywhere \|publisher=Microsoft \|website=[[MSDN]] \|date=28 April 2015 \|access-date=26 May 2017}}</ref> ==On-premises vs. online== Azure DevOps is available in two different forms: on-premises ("Server") and online ("Services").<ref>{{cite web\|url=https://codefresh.io/learn/azure-devops/\|title=What Is Azure DevOps? Services, Examples, and Best Practices\|website=codefresh.io}}</ref> The latter form is called [[Azure DevOps Services]] (formerly Visual Studio Online before it was renamed to Visual Studio Team Services in 2015). The cloud service is backed by the [[Microsoft Azure]] cloud platform. It uses the same code as the on-premises version of Azure DevOps, with minor modifications, and implements the most recent features~~. Azure DevOps requires no setup~~. A user [[sign in\|signs in]] using a [[Microsoft account]] to set up an environment, creating projects and adding team members. New features developed in short development cycles are added to the cloud version first. These features migrate to the on-premises version as updates, at approximately three-month intervals.<ref>{{cite web \|publisher=1105 Media \|year=2013 Line 52 ⟶ 48: ===Extensibility=== Microsoft provides two standalone redistributed [[application programming interface\|APIs]] for connecting to Azure DevOps. One is a [[Java (programming language)\|Java]] SDK, the other is a [[.NET Framework]] SDK. These APIs allow for client connectivity to Azure DevOps. Because Azure DevOps is written on a [[service-oriented architecture]], it can communicate with virtually any tool that can call a web service. Another extensible mechanism is subscribing to system alerts: for example, alerts that a work item was changed, or a build completed. There are approximately 20 preconfigured alerts, and teams can configure as many additional alerts as needed.<ref>{{cite web \|publisher=Microsoft \|year=2013 Line 69 ⟶ 65: ===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 96 ⟶ 92: \|title=How to customize TFS 2010 work items and workflows \|access-date=2013-10-17 \|archive-date=2013-10-19 }}</ref> Work items are combined into a '''Process Template''' that contains these and other pieces of information to provide a development framework. Azure DevOps includes Process Templates for the [[Microsoft Solutions Framework]] for Agile, Scrum and CMMI. Teams can choose to use a built-in template or one of the many templates available for use created by third parties. Process templates can be customized using the Process Template Editor, which is part of the Power Tools.<ref>{{cite web▼ \|archive-url=https://web.archive.org/web/20131019045206/http://tedgustaf.com/blog/2011/1/how-to-customize-tfs-2010-work-items-and-workflows/ \|url-status=dead ▲ }}</ref> Work items are combined into a '''Process Template''' that contains these and other pieces of information to provide a development framework. Azure DevOps includes Process Templates for the [[Microsoft Solutions Framework]] for Agile, Scrum and CMMI. Teams can choose to use a built-in template or one of the many templates available for use created by third parties. Process templates can be customized using the Process Template Editor, which is part of the Power Tools.<ref>{{cite web \|publisher=Microsoft \|year=2013 Line 109 ⟶ 108: ==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 150 ⟶ 149: Using Git does not preclude the benefit of using Azure DevOps work item or build system. When checking code in with Git, referencing the work item ID in the check-in comment will associate the check-in with the given work item. Likewise, Team Build will also build Git projects. One of the major reasons to use Azure DevOps as a Git repository is that it is backed by SQL Server and is afforded the same protection as Team Foundation Version Control (TFVC){{clarify\|date=September 2024}}. This gives developers some choices when choosing the type of project and work style that works best for them. ==Reporting== Line 172 ⟶ 171: ==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 186 ⟶ 185: \|title=Community TFS Build Extensions \|access-date=2013-10-17 \|archive-date=2013-10-11 }}</ref> and open source projects have been started to build community backed activities to enhance the capabilities of Team Build.▼ \|archive-url=https://web.archive.org/web/20131011050816/http://tfsbuildextensions.codeplex.com/ \|url-status=dead ▲ }}</ref> and open source projects have been started to build community backed activities to enhance the capabilities of Team Build. The build process can be configured for various types of builds including scheduled builds, [[continuous integration]], gated check-in and rolling builds. A gated check-in build will shelve code that a developer checks in, perform a "get latest" on the server code and perform a build. If the build succeeds, the code is checked in on behalf of the developer who submitted the code. If the build fails, the developer is notified and can fix the code before trying another check-in. Line 192 ⟶ 194: 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 Line 220 ⟶ 222: !Form !Release year !Version Number <ref>{{Cite web\|last=kexugit\|title=What version of Team Foundation Server do I have?\|url=https://docs.microsoft.com/en-us/archive/blogs/tfssetup/what-version-of-team-foundation-server-do-i-have\|access-date=2020-08-26\|website=docs.microsoft.com\|date=21 November 2013 \|language=en-us}}</ref><ref>{{Cite web\|last=\|title=Azure DevOps Feature Timeline\|url=https://docs.microsoft.com/en-us/azure/devops/release-notes/features-timeline#azure-devops-server-build-numbers\|access-date=2021-02-15\|website=docs.microsoft.com\|language=en-us}}</ref> \|- \|Team Foundation Server 2005 ~~\|Visual Studio 2005 Team System~~ \|On-premises \|2006 \|8 \|- \|~~Visual~~Team ~~Studio Team~~Foundation ~~System~~Server 2008 \|On-premises \|2008 Line 275 ⟶ 277: \|On-premises \|2017 \|1516 \|- \|Azure DevOps Services<ref>{{cite web \|last=Cool \|first=Jamie \|date=2018-09-10 \|url=https://azure.microsoft.com/en-us/blog/introducing-azure-devops/ \|title=Introducing Azure DevOps \|department=Blog \|website=[[Microsoft Azure]] \|publisher=[[Microsoft]] \|access-date=2019-10-13 \|df=mdy}}</ref> \|Cloud \|2018 \|16 \|- \|Azure DevOps Server 2019<ref>{{cite web \|last=Mackie\|first=Kurt \|date=2019-03-05 \|url=https://azure.microsoft.com/en-us/blog/now-available-azure-devops-server-2019/ \|title=Now available: Azure DevOps Server 2019 \|department=Blog \|website=[[Microsoft Azure]] \|publisher=[[Microsoft]] \|access-date=2019-10-13 \|df=mdy}}</ref> Line 288 ⟶ 290: \|- \|Azure DevOps Server 2020 \|On-premises \|RTW (Release to Web)<ref>{{cite web \|last=Mackie\|first=Kurt \|date=2019-03-05 \|url=https://azure.microsoft.com/en-us/blog/now-available-azure-devops-server-2019/ \|title=Now available: Azure DevOps Server 2019 \|department=Blog \|website=[[Microsoft Azure]] \|publisher=[[Microsoft]] \|access-date=2021-02-15 \|df=mdy}}</ref>▼ \|2020 \|18 \|- ▲\|~~RTW~~Azure ~~(Release~~DevOps toServer ~~Web)~~2022<ref>{{cite web \|last=~~Mackie~~Morales\|first=~~Kurt~~Gloridel \|date=~~2019~~2022-0312-0506 \|url=https://~~azure~~devblogs.microsoft.com/~~en-us/blog~~devops/now-available-azure-devops-server-~~2019~~2022-rtw/ \|title=Now available: Azure DevOps Server ~~2019~~2022 RTW \|department=Blog \|website=~~[[Microsoft~~ Azure]] DevOps Blog \|publisher=[[Microsoft]] ~~\|access-date=2021-02-15 \|df=mdy~~}}</ref> \|On-premises \|2022 \| \|} Line 296 ⟶ 303: * [[Comparison of version-control software]] * [[Comparison of issue-tracking systems]] * [[Microsoft Teams]] * [[Microsoft Visual SourceSafe]] (VSS) * [[List of version-control software]] * [[Rational Team Concert]] * [[SVNBridge]], a Windows client or server side extension to TFS that allows access to TFS revision controlled items from [[Subversion (software)\|Subversion]] client applications. * [[WinOps]] ==References== Line 307 ⟶ 314: ==External links== * {{Official website}} * [http://msdn2.microsoft.com/en-us/library/ms364061.aspx Team Foundation Server: At Work] * [http://msdn2.microsoft.com/en-us/library/aa302182.aspx Visual Studio 2005 Team System: Enterprise-Class Source Control] * [http://msdn2.microsoft.com/en-us/library/ms364074.aspx Using Source Code Control in Team Foundation] * [http://msdn2.microsoft.com/en-us/library/ms364062.aspx Team Foundation Server Fundamentals: A Look at the Capabilities and Architecture] * [http://msdn.microsoft.com/en-us/tfs2008/bb980951.aspx Visual Studio Team System 2008 Web Access] * [http://msdn.microsoft.com/en-us/library/fda2bad5.aspx Visual Studio Application Lifecycle Management] * [https://www.visualstudio.com/team-services/ Visual Studio Team Services] * [http://java.visualstudio.com/ Java Support in Team Foundation Server and Visual Studio Team Services] * [https://www.visualstudio.com/en-us/news/releasenotes/tfs2017-relnotes Team Foundation Server 2017 Release Notes] {{Version control software}} {{Microsoft Azure Services Platform}} {{Microsoft}} [[Category:Proprietary version control systems]] [[Category:Microsoft Visual Studio]]