Do you create a Continuous Integration Build for the Solution?

Last updated by TiagoAraujo about 7 years ago.See history

(Before you configure continuous deployment) You need to ensure that the code that you have on the server compiles. A successful CI build without deployment lets you know the solution will compile.

ci build 1
Figure: The Build definition name should include the project name. The reason for this is that builds for all solutions are placed in the same folder, and including the build name makes the Build Drop folder organised

ci build 2
Figure: On the Trigger tab choose Continuous Integration. This ensures that each check-in results in a build

ci build 3
Figure: On the Workspace tab you need to include all source control folders that are required for the build

ci build 4
Figure: Enter the path to your Drop Folder (where you drop your builds)

ci build 5
Figure: Choose the Default Build template and enter the DeployOnBuild argument to the MSBuild Arguments parameter of the build template

ci build 6
Figure: Queue a build, to ensure our CI build is working correctly

ci build 7
Figure: Before we setup continuous deployment it is important to get a successful basic CI build

We open source. Powered by GitHub