TFS2017 Continuous Integration Build

TFS2017 has been released for several months, after a few days of deployment and trial, TFS2017 's functional changes are really big. In particular, in terms of build-up changes, it has been declared in the Product Wizard that the XAML version controller and proxy have been deprecated, and it is recommended that you upgrade the build upgrade from the original 13 and 15 to the new production system, but at the same time, it is estimated that the reason for the preservation of forward compatibility is also provided in the XAML configuration pattern.

For the first time in the premise environment, the use of TFS2017 construction, or experienced some twists and turns, but after more than 10 attempts or the final construction success, small excitement also followed. Here's the whole process from preparing a project, creating a build definition to an integration build.

1, create a typical ASP. NET MVC project, and join the VC library.

Figure 1 Web project created based on vs built-in project template

2, create a build definition, where a few pits, to be properly configured, otherwise the construction is unsuccessful.

Figure 2 Specifying the build solution file

Figure 3 Configuring a shared folder as the publishing path

Figure 4 Specifying the publishing path

3, trigger build, automatically trigger when code is checked in, or trigger manually

Figure 5 Manually triggering the build

4, build results

Figure 6 Build results

The process above is relatively normal and simple, because TFS is a mature and very good product, many of the features of the user are out of the box. However, in the face of configuration administrators, installing and configuring the build agent requires some knowledge of the build mechanism of TFS.

TFS2017 's build agent can be deployed on any work machine that can connect to the TFS service, which is great, there is no need for tight coupling between the build service and the TFS Service, just to register the build agent on the server, and the process of registering is on the build server. You only need an account that has access to TFS. (developers can temporarily register their development environment as a proxy server and build their own projects on demand).

The configuration process is as follows:

Figure 7 downloading the agent from TFS

Figure 8 Installing the agent and starting as a service

Figure 9 Verifying that the service is started

TFS2017 Continuous Integration Build