Content deleted Content added
article not exist |
|||
| (23 intermediate revisions by 21 users not shown) | |||
Line 1:
{{short description|Source code management software}}
{{Infobox software
| name = Azure DevOps Server
Line 12 ⟶ 8:
| developer = [[Microsoft]]
| released = {{Start date and age|2005}}
| latest release version =
| latest release date = {{Start date and age|
| operating system = [[Microsoft Windows]]
| language =
Line 20 ⟶ 16:
}}
'''Azure DevOps Server''',
==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. 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 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 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 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 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
Line 291 ⟶ 293:
|2020
|18
|-
|Azure DevOps Server 2022<ref>{{cite web |last=Morales|first=Gloridel |date=2022-12-06 |url=https://devblogs.microsoft.com/devops/now-available-azure-devops-server-2022-rtw/ |title=Now available: Azure DevOps Server 2022 RTW |department=Blog |website=Azure DevOps Blog |publisher=[[Microsoft]]}}</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.
==References==
Line 307 ⟶ 314:
==External links==
* {{Official website}}
{{Version control software}}
{{Microsoft Azure Services Platform}}
{{Microsoft}}
[[Category:Proprietary version control systems]]
[[Category:Microsoft Visual Studio]]
| |||