After setting up Release Management Server, Client and Deployment Agent(s) configurations steps for VS Release Management should be done.
First step is setting up SMTP. This is a optional step, but necessary to configure for sending email notifications in release management workflows.
“Configure Apps” tab shows a guide for configurations, when VS Release Management Server is initially setup.
Click on “SMTP Server Settings” in “Configure Apps” tab or Click on Administration –> Settings to navigate to the settings tab.
Provide below (reference VS Release Management User Guide)
Server Name – Fully qualified address of the SMTP server to use.
Port – Optional. Port to be used when connecting to the SMTP server to send email notifications.
User Name – Optional. Name of the identity to be used to authenticate against the SMTP services.
User Password – Password of the identity to be used to authenticate against the SMTP services. Mandatory if User Name is specified. Otherwise, optional.
Sender Address – Email address as it will appear in the email client. No replies are expected to be sent to this address. Therefore, the email or text can be anything.
Once above configuration done Release Management Server is ready to send email notifications.
It is great if the latest updates to TFS can be applied as and when they are released. But for a large organization it might not be sometime...
Resolve MSB4019: The imported project "C:\Program Files\dotnet\sdk\1.0.0-rc4-004771\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Props" was not found or Unable to start the process. No executable found matching command "dotnet-projectmodel-server"You might encounter compilation error in Visual Studio 2015 when a new .NET Core 1 web app is created, if you have installed Visual Studio 2...
You needed to setup dedicated machines for testing when using Run Functional Tests and you had to execute, Deploy Test Agent step and Copy...
TFS 2018 RC1 is now available and you can download it from https://www.visualstudio.com/downloads/ . Release note here explains the new fea...
If you have upgraded the TFS from TFS 2015 to TFS 2018 you will encounter a situation where your vNext build agents 1.xx are no longer valid...