Shulou(Shulou.com)06/01 Report--

This article is a detailed introduction to "Jenkins how to compile. NET Core and. NET Framework projects and deploy them remotely to IIS". The content is detailed, the steps are clear, and the details are properly handled. I hope this article "Jenkins how to compile. NET Core and. NET Framework projects and deploy them remotely to IIS" can help you solve your doubts. The following is a small series of ideas to slowly deepen and learn new knowledge together.

Windows

First we install the appropriate environment on Windows.

Jenkins relies on JDK 11, please find the installation method yourself.

Jenkins installation directory defaults to C: \Windows\System32\config\systemprofile\AppData\Local\Jenkins.jenkins. Passwords/keys are generally in the secret-file file under its directory.

After installing Jenkins, open port 8080 to access Jenkins, and then install the plug-in according to the section "Use Jenkins Automation to Build. NET Core Applications under Linux_Install Plug-ins", and then install an additional powershell plug-in.

install Git

Next, install Git on Windows Server. The general Git installation directory is C:\Program Files\Git.

Then add the following two Git-related directories to the system environment variables:

C:\Program Files\Git\cmdC:\Program Files\Git\usr\bin

If you do not configure C:\Program Files\Git\usr\bin to the environment variable, you will get nohup error, Jenkins relies on nohup command.

WebDeploy

WebDeploy is an IIS remote deployment tool. Through WebDeploy, we can easily package applications for remote deployment to IIS without manual restart, replacement of website files, restart of program pool, etc.

After installation, the default installation directory of the program is:

C:\Program Files\IIS\Microsoft Web Deploy V3

Please add this directory to the system environment variable.

WebDeploy is also installed on the server to be remotely deployed.

Windows Slave Node

If you have a Jenkins Master server and then add Windows Jenkins Node as your master Jenkins, you can add Windows to your Linux node as follows:

If you only deploy Windows, Jenkins on Windows is the Master and you can skip this step.

Open the Master Jenkins Web interface, open Manage Jenkins in the left menu navigation, and then select Manage Nodes and Clouds in System Configuration.

Then add a new node "New Node".

The node name can be arbitrary. In the Label required to be filled in next, you need to fill in "windows". Of course, other identifiers are also available. However, labels are generally used to identify system characteristics. In addition, you will also be required to fill in the construction directory. This is the file used to store Jenkins 'work, such as pulling code and executing commands. All operations will be performed under this directory.

Click agent.jar in blue font to download java package.

Place the agent.jar package in the Windows where Jenkins resides, and then follow the prompts to launch agent.jar.

Just put agent.jar in the directory, then open powershell or cmd, copy Java -jar agent.jar -jnlpUrl above... Order, just execute it.

Then, in the Jenkins interface, you can see that another Windows slave has been added.

.NET Core

This section describes how to build and remotely deploy. NET Core applications to IIS.

For. NET Core applications, the process is relatively simple, you only need to install the. NET Core SDK, no additional operations.

Handling IIS

On the Windows server where you want to deploy the app, open IIS, click "Application Pool," and add a new one.

Next, add a website.

Then start adding a new user by clicking on the host name, then clicking on IIS Manager Users and adding a user.

Then enable WebDeploy deployment for the site.

Processing project Jenkinsfile

The author has uploaded the Demo project Jenkinsfile, readers can fork the project directly, and the sample project is in the coreiis branch.

https://github.com/whuanle/DotNetCoreJenkinsDemo/tree/coreiis

Then download the source code and modify the Jenkinsfile.

// IIS configuration, remotely published variables IISTMP = 'C:/webdemo_tmp' //Temporary directory for packaged publishing IISAPP = 'jenkinsdemo.com' //Website name IISADDR = 'https://192.168.0.66:8172/msdeploy.axd' // WebDeploy's address IISUSER = 'jenkinesdemo' //Account password used to log in to IIS IISADMIN = 'jenkinesdemo'

According to the author's demo, readers only need to modify the IP and username or password in IISADDR.

Then, using Jenkins, add pipeline deployment. I won't repeat the new process on Jenkins here. Readers can refer to another article by the author:

Build. NET Core Applications Automatically with Jenkins on Linux_Build Pipelines

.NET Framework

In order to compile. NET Framework applications, we need to build a compilation environment for. NET Framework applications. Since. NET Framework relies heavily on Vistual Studio, if you leave VS environment, you need to install many environment tools to use command compilation programs. It is more troublesome and readers need to be patient.

Example projects have been uploaded to www.example.com. https://github.com/whuanle/DotNetCoreJenkinsDemo/tree/fxiis

Installation Environment. NET Framework SDK

The. NET Framework package provides an environment for compiling and running. NET programs.

Installs the. NET Framework in various versions, depending on the version required for the project being compiled.

For example. NET Framework 4.6.1 and. NET Framework 4.6.1 Developer Pack.

Download address: dotnet.microsoft.com/download/dotnet-framework

MSBuild

MSBuild is a compilation tool for. NET programs that can be used outside of VS environments.

If you want to compile a. NET Framewrok project, such as 4.6, use MSBuild 14(corresponding to VS 2015) with the generic file name BuildTools_Full_14.exe.

Download Address:

https://www.microsoft.com/en-US/download/details.aspx? id=48159

https://github.com/EWSoftware/SHFB/releases

After MSBuild is installed, its directory location is:

C:\Program Files (x86)\MSBuild\14.0\Bin

Add its directory path to the system environment variable.

Nuget

nuget is used to restore project dependencies. For. NET Framework projects, the version of nuget cannot be above 5.0. It is recommended to use version 4.5 or so, otherwise there will be compatibility problems!

After installation, the nuget program directory is:

C:\Program Files\nuget

Add directories to system environment variables.

After installing the required tools, you need to add the following items to the environment variables:

C:\Program Files (x86)\MSBuild\14.0\BinC:\Program Files\Git\cmdC:\Program Files\nugetC:\Program Files\Git\usr\binC:\Program Files\IIS\Microsoft Web Deploy V3

Please check carefully if there are any remaining items.

configuration item

To automate building. NET Framework applications out of VS environments, there are a lot of configuration files and environments to deal with, and we need to modify the project a bit. In this section, you'll learn how to configure the build of the. NET Framework automation pipeline, configure the pipeline using Jenkins, write Jenkins scripts, and more.

Generally, in a solution, there is a main program that needs to be published (mainly Web applications). Please add Nuget references for Web projects that need to be published, search MSBuild.Microsoft.VisualStudio.Web.targets package, and add references to the project.

Because. NET Framework projects rely on Viual Studio distribution, there are a lot of problems if you don't use VS distribution, and in order to get out of the VS environment, someone encapsulates a complete targets file that instructs MSBuild how to compile this program.

Web publishing properties need to be defined for Web projects that need to be published. In automated builds, depending on these preconfigured properties, these properties will generate a.pubxml file that will be uploaded to the repository along with the source code.

Then click Publish to manually publish one directory at a time.

After saving the settings, in the Properties\PublishProfiles directory of the project, you can find the FolderProfile.pubxml file, which has a line of PublishUrl attribute, which is the output directory when the website is published.

C:\test

This directory configuration will affect the output of the automated build. When compiling, the generated files will be output to this directory. Please ensure that this drive letter is stored in Windows Jenkins!

And then directly on Jenkins Web, you can operate it.

anteroposterior classification scheme

When we finish creating the website for the. NET Core /. NET Framework project, the application is packaged with the front end, which is inconvenient to publish.

We can create a new useless website for our front-end project.

I can write pipeline scripts that automatically package front-end files for publishing to this site via WebDeploy.

Next, in the backend site, add a virtual directory that matches the directory of the front-end site.

In this way, both the front and back end can be deployed separately, while the front-end files can be read directly after the back-end website.

Read here, this article "Jenkins how to compile. NET Core and. NET Framework projects and remote deployment to IIS" article has been introduced, want to master the knowledge points of this article also need to be hands-on practice to understand, if you want to know more about the content of the article, welcome to pay attention to the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.