Azure DevOps Server: Difference between revisions

Revision as of 11:49, 4 May 2024

Latest revision as of 09:50, 26 July 2025

(8 intermediate revisions by 8 users not shown)

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]]