MSBuild

The MSBuild plugin allows you to use MSBuild to build .NET and Visual Studio projects within Jenkins.

• Pipeline Configuration
• Free Style Job Configuration
• Tools Setup
• Known Issues and Workarounds

Here's an example Jenkins declarative pipeline script for utilizing the MSBuild plugin:

pipeline {
    agent any
    tools {
        msbuild 'MSBuild 2022'
    }
    stages {
        stage('Build') {
            steps {
                script {
                    bat 'msbuild right-first-time.sln /p:Configuration=Release %MSBUILD_ARGS%'
                }
            }
        }
    }
}

On your project configuration page, specify the name of the build file (.proj or .sln) and any command line arguments you want to pass in. The files are compiled to the directory where Visual Studio would put them as well.

To use this plugin, specify the location directory of MSBuild.exe on Jenkins' configuration page. The MSBuild executable is usually situated in a subfolder of C:\\WINDOWS\\Microsoft.NET\\Framework. The Visual Studio Build Tools 2022 version of "msbuild.exe" is located in "C:\\Program Files (x86)\\Microsoft Visual Studio\\2022\\BuildTools\\MSBuild\\Current\\Bin\\". If you have multiple MSBuild versions installed, you can configure multiple executables.

• When using Command Line Arguments, bear in mind that special characters are treated like in Unix, so they will need to be escaped using the backslash.

• Using the option /nr:false (node reuse=false) ensures that the spawned build processes are terminated as soon as the parent process completes, which resolves the issue of build stalls. Since the plugin waits for all spawned processes to finish, this option should be considered implicit. JENKINS-56234.