Visible Studio Staff Providers (VSTS), Microsoft’s software lifecycle administration system, is to endure a significant shake-up and rebranding. As a substitute of a single Visible Studio-branded service, it is being cut up into 5 separate Azure-branded providers, underneath the banner Azure DevOps.
The 5 parts:
Azure Pipelines, a steady integration, testing, and deployment system that may hook up with any Git repository
Azure Boards, a piece monitoring system with Kanban boards, dashboards, reporting
Azure Artifacts, a internet hosting facility for Maven, npm, and NuGet packages
Azure Repos, a cloud-hosted non-public Git repository service
Azure Check Plans, for managing exams and capturing knowledge about defects.
VSTS has been damaged up on this option to additional Microsoft’s ambition of creating its developer tooling helpful to any growth course of and workflow, no matter language or platform. The division into particular person parts ought to make it simpler for builders to undertake parts of the Azure DevOps platform, with out requiring them to go “all in” on VSTS. The diminished scope of every element implies that it is cheaper than the VSTS pricing, making incremental adoption extra palatable. For instance, a Pipelines course of might construct and check a Node.js service from a GitHub repository after which deploy to a container on Amazon’s AWS cloud, with out requiring use of any of the opposite Azure DevOps parts.
Microsoft can also be making Pipelines out there at no cost for open supply tasks. Open supply builders may have limitless construct time and as much as 10 parallel jobs. Pipelines has Home windows, macOS, and Linux techniques for testing, making it appropriate for a variety of tasks, and the Atom and Visible Studio Code editors, and CPython and TypeScript programming languages, are already utilizing Azure Pipelines for his or her constructing and testing. Azure Pipelines can also be out there via the GitHub Market, making it simpler to plumb into GitHub repositories.
Current VSTS prospects may have their tasks migrated to Azure DevOps mechanically; some URLs will change, however performance ought to stay the identical. This continuity explains one of many much less apparent components of Azure DevOps: Azure Repos. With Microsoft on monitor to purchase GitHub, topic to regulatory approval, a second cloud-based Git repository service appears superfluous. Nonetheless, Azure Repos is designed as an similar drop-in substitute/rebranding for the present VSTS Git internet hosting functionality.
That is additionally related to customers of the on-premises Staff Basis Server, the approximate on-premises equal to VSTS. That product will probably be renamed to Azure DevOps Server, and can proceed to trace the cloud model (albeit with much less frequent updates), so builders that do not or cannot use the cloud for no matter purpose will proceed to have an possibility.