Azure DevOps Server: Difference between revisions

Content deleted Content added
Citation bot (talk | contribs)
Added date. | Use this bot. Report bugs. | Suggested by Whoop whoop pull up | Category:Bug and issue tracking software‎ | #UCB_Category 23/45
article not exist
 
(11 intermediate revisions by 11 users not shown)
Line 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==
Line 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 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 314:
==External links==
* {{Official website}}
* [https://learn.microsoft.com/en-us/azure/devops/?view=azure-devops Azure DevOps documentation] on [[Microsoft Learn]]
 
{{Version control software}}
{{Microsoft Azure Services Platform}}
{{Microsoft}}
 
[[Category:Proprietary version control systems]]
[[Category:Microsoft Visual Studio]]