Set up CI server with Jenkins

　　Jenkins It's an open source, cross platform CI Tools , It can be deployed in Windows、Linux Platforms such as , also Jenkins Provides a very rich set of plug-ins to help complete the compilation 、 test 、 Deployment, etc . 　　 This article will introduce you to Windows On the platform Jenkins complete .Net Core Build a continuous integration environment for applications , The main contents are as follows ：

• Jenkins Download and install
• Create a .Net Core Compilation task
• Realize automatic test
• Implement automatic deployment
• Summary

Jenkins Download and install

　　 This example USES Jenkins2.136 Version to demonstrate ,Jenkins Download address ：https://jenkins.io/download/ 　　1. download Jenkins Of Windows Installers ：

　　2. Complete the installation wizard Jenkins install ：

　　Jenkins The default port is 8080, When the installation is completed, you can access... Through this port Jenkins：

　　3. according to Jenkins The configuration wizard completes the corresponding configuration , And enter Jenkins： 　　 Select common plug-ins , These plug-ins contain Git、SVN And other common plug-ins ：

　　 Create user ：

　　 Get into Jenkins：

Create a .Net Core Compilation task

　　1. Create a new task ：

　　 Fill in the task name and choose a free style project ：

　　2. Modify task configuration ：

　　 The code base ：

　　3. Add build steps , Here to perform dotnet The compile command of ：

　　4. Perform tasks , The output is as follows ：

Realize automatic test

　　1. Add test run steps ：

　　dotnet Test command reference ：https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-test?tabs=netcore21 　　 Running results ：

　　2. Collect code coverage ： 　　 The use of OpenCover To analyze .net core Unit test code coverage , And then through ReportGenerator To generate Html Report in format , So first, you need to add the construction steps of code coverage analysis and report generation ：

　　OpenCover.Console.exe -target:"dotnet.exe" -targetargs:"test XUnitTestProject/XUnitTestProject.csproj" -output:coverage.xml -filter:"+[*]* -[*Moq]* -[xunit*]*" -oldstyle 　　ReportGenerator.exe "-reports:coverage.xml" "-targetdir:report" notes ： Use... In continuous integration tools OpenCover Code override information may not be generated , So you need to OpenCover.Profiler.dll File registration , The registration code is as follows ：

　　OpenCover.Profiler.dll The file is located in OpenCover Installation directory , For more details OpenCover Install under directory Usage.rtf file .

　　 If you want to generate Html stay Jenkins Displayed on the , Then you must add a HTML Publisher Plug in for ：

　　 Then add... In the post build operation HTML Publish operation ：

　　 Need to fill in HTML Table of contents and report start page . 　　 Save the configuration when you're done , And build ：

　　 Then you can view the code coverage report in the engineering panel ：

　　 The report ：

Implement automatic deployment

　　 When the compilation is complete , You need to publish the compiled results , For one Windows For console applications , In fact, the edited execution program and related assemblies can be published , And this program file is actually in the project bin Under the table of contents . stay Jenkins Through Artifact Deployer Plug-in This plug-in to complete the file publishing function ：

　　 When the plug-in is installed , Add a deployment operation to the post build operation of the project , Copy the generated file to D:\test Under the table of contents ：

　　 After the build is executed, the build results will be automatically published to D:\test Under the table of contents .

Summary

　　 This article briefly introduces how to use Jenkins And related plug-ins .Net Core Automatic compilation of programs 、 Test and release features . Whether using various hosting tools mentioned in the previous article or building your own Jenkins Its core steps are completed by executing commands through corresponding tools ( Compile command 、 The test command 、 Code coverage command 、 Report generation commands, etc ).

　　 Although all through the same tools and the same commands , But different CI There are still some differences in the use of tools , And there are a lot of manual configurations , Is there a way to simplify and reuse CI/CD How about the process ？ Please look forward to the following (*^_^*)