Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 24.4

Release Management for Visual Studio
Release Management for Visual Studio Technology

General InformationGeneral Information help

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website: Go to site
Description: Release Management for Visual Studio is a service in Visual Studio Team Services (VSTS) and Team Foundation Server (TFS, Update 2 and later). This service is an element of development operations (DevOps) that allows users to fully automate the testing and delivery of software in multiple environments all the way to production or set up semi-automated processes with approvals and on-demand deployments.

This technology utilized a Microsoft SQL Server database to store data pertaining to release pipelines, environments, tasks, releases, and deployments.

Note: The 2015 release of this technology is the last stand-alone version of this software. After this release the functionality of this technology was integrated into the Build and Release hub in Team Foundation Server (TFS) and Visual Studio Team Services (VSTS). The scope of this entry only covers the stand-alone versions of the software.
Technology/Standard Usage Requirements: Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information: This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at
Decision: View Decisions

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v21.12
Decision Date: 12/13/2021 at 17:38:28 UTC
Aliases: Install Release Management server; Install Release Management client
Introduced By: TRM Request
Vendor Name: Microsoft
- The information contained on this page is accurate as of the Decision Date (12/13/2021 at 17:38:28 UTC).