Reputation: 1344
Trying to setup automated releases using Release Management for Visual Studio 2013. Process works when manually creating a release in RM Client.
When queuing a new build in Visual Studio, build succeeds, but release never displays in RM.
"Release Build" is set to "True" in Build Template.
Any suggestions?
Upvotes: 1
Views: 297
Reputation: 4547
Other than what @DanielMann correctly said in his answer, there are two important flags to consider:
Release Build
needs to be set to True
(as mentioned by the OP)Can Trigger a Release from a Build?
checkbox must be checked. The checkbox can be found in the Release Management client, in the Properties of a specific Release Template. That's also the section where one can specify the Build Definition to use for the Release.See the Trigger a release from a build documentation on MSDN.
Upvotes: 0
Reputation: 1344
In the build template, "Configuration to Release" was set to "Release - Any CPU". After removing, the Release build process was triggered.
Upvotes: 1
Reputation: 59035
If you're using an agent-based release template, the release management client has to be installed and configured on your build agent.
If you're using a vNext release template, the release build process template will not work. You'll have to customize it to use the REST API that was added in Update 3.
Upvotes: 1