Visual Studio Team Services (VSTS), Microsoft’s software lifecycle control machine, is to go through a significant shake-up and rebranding. Instead of a unmarried Visual Studio-branded provider, it is being break up into five separate Azure-branded products and services, below the banner Azure DevOps.
The five elements:
- Azure Pipelines, a continual integration, trying out, and deployment machine that may attach to any Git repository
- Azure Boards, a piece monitoring machine with Kanban forums, dashboards, reporting
- Azure Artifacts, a internet hosting facility for Maven, npm, and NuGet applications
- Azure Repos, a cloud-hosted personal Git repository provider
- Azure Test Plans, for managing exams and taking pictures knowledge about defects.
VSTS has been damaged up on this manner to additional Microsoft’s ambition of creating its developer tooling helpful to any building procedure and workflow, irrespective of language or platform. The department into person elements will have to make it more uncomplicated for builders to undertake parts of the Azure DevOps platform, with out requiring them to cross “all in” on VSTS. The lowered scope of each and every part implies that it is inexpensive than the VSTS pricing, making incremental adoption extra palatable. For instance, a Pipelines procedure may build and check a Node.js provider 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 elements.
Microsoft may be making Pipelines to be had free of charge for open supply tasks. Open supply builders could have limitless build time and up to 10 parallel jobs. Pipelines has Windows, macOS, and Linux methods for trying out, making it appropriate for quite a lot of tasks, and the Atom and Visual Studio Code editors, and CPython and TypeScript programming languages, are already the use of Azure Pipelines for his or her construction and trying out. Azure Pipelines may be to be had in the course of the GitHub Marketplace, making it more uncomplicated to plumb into GitHub repositories.
Existing VSTS shoppers could have their tasks migrated to Azure DevOps robotically; some URLs will trade, however capability will have to stay the similar. This continuity explains probably the most much less evident portions of Azure DevOps: Azure Repos. With Microsoft on target to purchase GitHub, topic to regulatory approval, a 2d cloud-based Git repository provider turns out superfluous. However, Azure Repos is designed as an an identical drop-in alternative/rebranding for the present VSTS Git internet hosting capacity.
This may be related to customers of the on-premises Team Foundation Server, the approximate on-premises similar to VSTS. That product will probably be renamed to Azure DevOps Server, and can proceed to monitor the cloud model (albeit with much less common updates), so builders that do not or cannot use the cloud for no matter explanation why will proceed to have an possibility.