ms-release-management

ms-release-management

where is the "Build Drop Location" defined in Release manager 2013

How do I override the Validator's approval and move the release to a next stage in Microsoft Release Management?

Release Management 2013 stuck on deployment step

How to reference Script Arguments in DSC Script Resource

Release Management 2015 Update configuration variables during release

How can I troubleshoot vNext Release Management 2015 404 errors

Release Management Online Tokenization not working

Using TFS Release Management with a DSC pull server

DSC: How to stop and start a windows service

Can't connect Release Management client for Visual Studio to VSTS

Release Management 2015 randomly hangs during acceptance/approval/validation/deployment steps

"The system cannot find the file specified" on custom tool

Deploying WebSite builds to Azure from VSTS Release Management

Build not set indefinitely by RM

Microsoft Release Management - build fails with Internal Server Error

visual studio release management 2013 "Copy File or Folder" does not work with build variable

Base-64 error when trying to execute vNext deployment script

Release Management 2013 with TFS 2015

Failed to deploy component - "Cannot deserialize the current JSON object ..."

Why Installer made with installshield hangs when deployed using ReleaseManagementBuild.exe?

Create bug on failed release

System Variables in vNext release template

ReleaseManagement InitiateRelease REST API call returns 500 error

How to get logs into the Tool Log in Release Management for Visual Studio

RM + DSC to node in untrusted domain

Release Management 2013 - getting Deployment Agent 2013 Error when deploying to a server with Enterprise Library 5.0 Installed

MS Release management clean up of drop folders

Releases stuck in 'Rejected' state

Release Management Server Installation Issue - object already exists

TFSBuild / Release Manager: The directory name is invalid

Release action stuck in "Pending" status for hours

Failed to configure Release Management service user. Error: The remote server returned an error: (401) Unauthorized

Microsoft Release Management timeout during deploy step

Release Management 12 - Create Web Site with Host Header

Team Foundation Server 2013 Release Management Scheduled Deployments

Components are exposed for all users?

page:1 of 1 main page

Categories

azure-cognitive-search

unet-neural-network

google-cloud-pubsub

metadata-extractor

screen-scraping

android-textinputlayout

microsoft-identity-pla...

linear-discriminant

python-constraint

connection-string

visual-studio-debugging

material-components

nestjs-passport

advanced-rest-client

apache-commons-math

o365security-compliance

xcode-build-settings

asp.net-core-configura...

laravel-upgrade

vcloud-director-rest-api

android-preferences

combinedresourcehandler

jquery-ui-accordion

esri-javascript-api

django-debug-toolbar

codeigniter-restserver

state-restoration

computer-science-theory

windows-live-id

castle-activerecord

windows-networking

iequalitycomparer

mkannotationview

Resources