Here we'll show you how to define your continuous integration (CI) process for your Azure cloud service project.
Get set up
For the instructions in this topic, you need an Azure cloud service project in Visual Studio.
If you don't yet have an app but want to try this out, then see the Q&A below.
Define your CI build process
Create the build definition
(If you don't see your team project listed on the home page, select Browse.)
- On-premises TFS:
- Visual Studio Team Services:
- On-premises TFS:
- Select the Azure Cloud Service template.
- As the repository source, select the team project, repository, and branch.
- Remove the Azure Cloud Service Deployment task from the build definition, since you will be deploying the cloud service later through a release definition.
Enable continuous integration (CI)
On the Triggers tab, enable continuous integration (CI). This tells the system to queue a build whenever someone on your team commits or checks in new code.
Queue and test the build
Save the build definition and queue a new build by selecting the Queue new build command. Once the build is done, click Artifacts and then Explore to see the cloud service package (.cspkg file) produced by the build. This is the package that your release definition will consume to deploy your app.
Deploy your app
After you've run the build, you're ready to create a release definition to deploy your app to:
How do I create an Azure cloud service solution?
In Visual Studio, connect to your team project.
On the Team Explorer home page (Keyboard: Ctrl + 0, H), under Solutions, click New.
Select the Cloud templates section, and then choose the Azure Cloud Service template.
When prompted for the roles in the cloud service, choose the ASP.NET Web role to the project.
When prompted for the type of ASP.NET project for the Web role, choose the MVC project.