Continuous Integration ~ Jenkins builds a dotnetCore project, jenkinsdotnetcore

Continuous Integration ~ Jenkins builds a dotnetCore project, jenkinsdotnetcore

 

Last week, a major component was the release of dotnet core2.0. NET Standard2.0 has also been released, and the entire Microsoft ecosystem is excellent. Of course, there is also a BUG. For example, EFCore's support for Mysql is still flawed compared with 1.1, this is a good solution. Today we will mainly talk about how to integrate jenkins and dotnetCore into jenkins for persistent integration after they are installed in windows!

• Install the dotnet core sdk 2.0
• Install jenkins
• Create a core project on github
• Start our CI journey

Dotnet is a command package

After jenkins is installed, it is hosted in windows service as a service. port 8080

Build our core solution on github and create a console program for CI integration!

Deploy our scripts in jenkins in three steps: one step is to pull the latest code from the server, the other step is to build the dotnet to restore the package, build the project, and release the project to the local directory, send the generated code to the server in three steps.

Note that the plug-in added here is windows batch command. To avoid the trouble caused by space in the path, we add double quotation marks to the path. Otherwise, it will be considered as two projects.

The synchronization code is still written using powershell, which is relatively fixed.

After an automatic project is created, the project has console log output, which can be used for troubleshooting!

Now, the deployment is complete!

Next, let's talk about the cooperation between jenkins and docker!

Thank you for reading!