Update: Friday, 12 February 2016 10:40 UTC
Hotfix deployment is in progress to address this issue and once the fix rolls out across all the account the issue will be completely mitigated.
Next Update: Once the hotfix deployment completes.
Sincerely,
VS Team Services Service Delivery Team
Update: Friday, 12 February 2016 15:40 UTC
Our DevOps team has identified the root cause and working on a fix. Until we deploy the fix, there is a workaround for the issue. please follow below documented steps.
- Work Around:
- https://blogs.msdn.microsoft.com/visualstudioalm/2016/02/12/impact-of-new-release-management-orchestration-features/
- Next Update: 4 Hours
Sincerely,
VS Team Services Service Delivery Team
Initial Update: Friday, 12 February 2016 12:24 UTC
We are actively investigating issues with Issues with Release Management under VS Team Services. A subset of customers in South Central US may not be able to deploy a release manually to an environment. The automated deployments will work fine.
Next Update: 5 Hours
We are working to resolve this issue and apologize for any inconvenience.
Sincerely,
VS Team Services Service Delivery Team