This is the first blog post of two about Jenkins and Couchbase. This first post is a general introduction to Continuous Deployment: you’re going to learn to use Jenkins to deploy a .NET application automatically. The second blog post will be focusing more on how to use Jenkins to set-up test data in Couchbase before running your test code.

As a .NET developer you are probably using Visual Studio. Hitting F5 in Visual Studio compiles the source code and starts the debugger. If you are like me you will hit F5 many times during development and bug hunting.

But what happens when the code is ready for prime time? Deployment happens!

When I need to publish an application I often choose the laziest option: manually copying the executable to the destination, manually installing and manually starting the application.

It’s “fun” the first few times, but in the end it gets really difficult; particularly keeping track of changes and manual updates/deployments. To be honest, this manual approach does not scale very well: it takes unnecessary time and it’s prone to human errors in the deployment process.

A more mature option would be to have an automated infrastructure to handle deployment. Such infrastructure is often referred to as Continuous Integration/ Continuous Deployment.

Using Continuous Integration/Continuous Deployment, enables a workflow like this:

  • Code, build and test locally on your dev. box (as usual)
  • Check source code into a development branch in your favourite Source Control Management System.
  • Optional code review by team members.
  • Merge your changes to the main (release) branch.
  • The CI Server will detect the changes to the main branch and download, compile and deploy/install your application on the release server.

There are no manual steps: it’s all scripted and automatic.

Continuous Deployment

You can choose from a number of Continuous Integration/Deployment (CI) tools, each with its own caveats. In my set-up I need a CI Server that understands the components in my application.

So let’s take a closer look at my application architecture and components:

  • Platform: .NET 4.5.2
  • IDE: Visual Studio 2015 (MSBuild files)
  • Application type: Windows Service
  • NuGet: Package Manager used for all references.
  • Source Control: Git (

The CI Server should be able to understand all components mentioned above and (as I’m lazy) it should be really easy to maintain and set up.

I did a bit of research and from other people’s experiences and blog posts I found it best to use Jenkins to deploy a Windows service.


Jenkins is a build server with a plugin architecture that allows the community to extend what Jenkins can “understand”. This architecture makes it easy to extend Jenkins to support MSBuild files, Git version control etc.

Meet Jenkins


Jenkins is installed on a build server. In my set-up the build server is the same as the release server, but this can be configured differently.

Download and install Jenkins for your platform here:

After installation Jenkins is available on its default port: http://localhost:8080/

Configure Jenkins

Jenkins has plugins for understanding Git repositories, MSBuild files and various other technologies. In the current set-up we only need to extend Jenkins with those two plugins.

Install the Git Plugin for Jenkins:

  1. Open Jenkins, http://localhost:8080/
  2. Navigate to “Manage Jenkins”
  3. Navigate to “Manage Plugins”Direct link: http://localhost:8080/pluginManager
  4. Use the “filter” box to search for “Git plugin” and install the plugin.

Install the MSBuild Plugin for Jenkins:

  1. Open Jenkins, http://localhost:8080/
  2. Navigate to “Manage Jenkins”
  3. Navigate to “Manage Plugins”Direct link: http://localhost:8080/pluginManager
  4. Use the “filter” box to search for “MSBUILD plugin” and install the plugin.plugin screenJenkins now understands MSBuild files and Git source control, but we still need to configure the MSBuild Plugin with a path to the msbuild.exe we would like to use.

MSBuild configuration

When the MSBuild plugin was installed it added its own configuration options to the Jenkins global configuration page.

  1. Navigate to http://localhost:8080/
  2. Click “Manage Jenkins”
  3. Click “Configure System”
  4. Scroll down the list until you find “MSBuild”
  5. Click the “MSBuild installations…” button
  6. Click “Add MSBuild”
  7. Give the new MSBuild configuration a name like “MSBuild-default”.
  8. In the path field, insert the fully qualified path to msbuild.exeOn my server the path is: C:Program Files (x86)MSBuild14.0Binmsbuild.exe, but this can be different on your system.Read below for more information about MSBuild and how to install it.
  9. Click save.

plugin screen

MSBuild installation

MSBuild is installed with Visual Studio, it’s the build system that Visual Studio uses when you select “build” or hit “F5”.

It’s not always feasible or even possible to install Visual Studio on your build machine. This could be due to license and security issues etc.

To accommodate this Microsoft has released a separate package called: “Microsoft Build Tools 2015” that contains all you need for using MSBuild.

Direct download:

After successful installation you have MSBuild available on the build server and with that you get the path value for step 8, above.

With this step done Jenkins is ready to build and deploy with MSBuild and Git.

Create a new Jenkins build project

It’s now time to point Jenkins to the source code and start building.

  1. Open Jenkins, http://localhost:8080/
  2. Select “new”.Direct link http://localhost:8080/view/All/newJob
  3. Give the project a name “Windows Service Deployment” or something you can remember.
  4. Select “Freestyle project”.
  5. Select “Ok”.plugin screen
  6. Next, expand the “Source Code Management” region by selecting “Git”.plugin screen
  7. Complete the Git configuration by filling in the blanks with a URL to your repository and optionally credentials (if needed).Jenkins can also work with branches. In this set-up I will leave the branch as the default (Master) but you can select whatever fits your needs.If you don’t already have a Git repository ready for testing, you can use the pre-cooked repository here: source code contains a few more files than your average “Hello Windows Service” solution. I will explain relevant parts later on as they are used. For now we will just treat this as a “Hello World” solution.
  8. If you haven’t done so already, click “Save” to persist your changes and navigate back to the main “Project” page.

Testing the Git configuration

Now we can test if the Git Source Management tab has been configured correctly and that we can clone the source code.

We are not yet building anything, only cloning the source. Building will come in a moment. First, let’s make sure Jenkins can clone the source from the repository.

  1. Navigate to the “Project” page
  2. Click the “Build Now” to start a “Build”.plugin screen
  3. In the “Build History” region you should now see a build in progress with the name “#1”.
  4. If every completes as expected “SUCCESS” then the bubble maker stays blue, if not it goes red.
  5. To see the build details, click the build number “#1”
  6. Then click “Console Output”. You should see something similar to what I have here:

    *What’s important to note here is the path to the “workspace” as this is where the source code is downloaded to and built from. This knowledge can be very helpful when debugging the CI setup.*

Building the source

The next step is to compile and build the source code.

  1. Navigate to the “project” page
  2. Select “Configure”
  3. Find the “Add build step”image
  4. Select the “Build a Visual Studio project or solution using MSBuild”.We need to configure a few values here:
    1. First, select the MSBuild version (we configured this in a previous step).
    2. Then give the path to the *.sln or *.proj file for your project.For the pre-cooked repository the path is: srcMyWindowsServiceMyWindowsServiceDeploy-Windows-Service-Via-MSBuild.projPlease note: We are not pointing to the solution file, rather we are pointing to a custom MSBuild file that is in the project. This MSBuild file is handling all steps involved with compiling and deploying the Windows Service.If you are using the pre-cooked repository, your setup should look like this:image
    3. Click save

NuGet package restore

If we were to build the project right now it would fail due to missing NuGet packages. Therefore we need to restore the NuGet packages before attempting to build the source.

nuget.exe makes this task very easy, we simply need to fire this command on the solution file:

nuget restore "path to *.sln" file

No surprise Jenkins can handle multiple build steps, so let’s add a build step to enable NuGet restore.

  1. Navigate to the “project” page.
  2. Select “Configure”.
  3. Find the “Add build step”.
  4. Click “Add build step”.image
  5. Select “Execute Windows batch command”.
  6. Re-arrange the build order by dragging the new build step to the top.image
  7. In the Command field insert:nuget restore srcMyWindowsService
  8. Click “Save”.

We are now ready to build the project!

The final test! Primetime!

  1. Navigate to the project page
  2. Click the “Build now” link
  3. Wait for the build to complete
  4. Open “Windows Explorer” and navigate to C:
  5. Confirm that the file “MyWindowsService.log” existsimage
  6. Open the file and read the log content.This file was create by our newly installed Windows Service!
  7. Check that the Service is installed and running:
    1. On Windows open “Services” management window
    2. Scroll down to you find the service “My Windows Service (…)”image

Congratulations! You have now successfully configured Jenkins to download, compile and deploy a .NET Windows Service! Automation ROCKS!

The source code:

So far we have not given much attention to the source code, but let’s take a moment to walk through the repository content and structure.

If you navigate to the repository root at:

you will find all the usual files as README etc. but also a file called nuget.exe.

nuget.exe is the executable used to restore the solution’s NuGet package dependencies. You could argue whether or not it’s good practice to have binary files in your source control, but in this case it’s a required dependency for the build system and therefore I have included it.

I have placed nuget.exe in the root, to keep it separated from the actual source code and make it easy to find when setting up the build in Jenkins.

If we navigate deeper into the repository to src/MyWindowsService/MyWindowsService/ we find four files that do all the hard lifting of compiling and installing the Windows Service.

The main entry point file is Deploy-Windows-Service-Via-MSBuild.proj it’s a MSBuild file constructed to, not only, compile the source code; but also: stop, uninstall and start the Windows Service application. This is achieved by calling the three batch files as needed: safeServiceDelete.bat, safeServiceStart.bat and safeServiceStop.bat.

It’s out of the scope for this blog post to explain in detail what each of the four files do, but if you take a look at the files individually I’m sure you will get a very good understanding of their inner workings and how they collaborate.

The Windows Service source code can be viewed and edited in Visual Studio to fit your specific needs. The sample source given in the repository is very simple and only writes a few entries to a text file (log file) and also “upserts” a document to Couchbase Server:


If you are new to Couchbase I would suggest taking a look at our .NET tutorial here:


Create your own

The easiest way to use Jenkins and .NET to build and deploy your own automated Windows Service would most likely be to clone this repository and change the service code in Visual Studio to suit your needs.

Thanks for reading!


Posted by Martin Esmann, Developer Advocate, Couchbase

Martin Esmann is a .Net Developer Advocate at Couchbase. He is a passionate developer with a deep focus on Microsoft Technologies like .NET.


  1. Nice Post Martin,
    Can you please elaborate more on installing the NuGet package restore.
    As faar as I know, NuGet package manager requires in Visual Studio to install any packages which will be used in the project.
    Once the package is installed DLLs are added in ‘bin’ folder, which will be used in the deployment packages.
    So what is the exact use of NuGet package restore here ?

  2. Andy,
    The nuget.exe Martin references in the post is the command line version of the package manager built into to VS (it’s available at The typical flow for a CI server is:
    * Check out latest code
    * Restore packages (command line: nuget restore)
    * Compile using MSBuild
    When you do a nuget restore, the packages aren’t placed into the bin folder – that’s for the compiled binaries after build. The nuget dependencies go into a packages directory (typically at the same level as your solution file) and then MSBuild does all of its magic.

  3. How do you managed to deploy Windows Service with MSBuild? Could you give more insight?

  4. Thanks for sharing with us. I just loved your way of presentation. I enjoyed reading this .Thanks for sharing and keep writing. It is good to read blogs like this. Dot Net Training

  5. Great guide! Just one question – everything works for me except for the NuGet package restore step. That gives me the following errors:

    WARNING: The remote server returned an error: (404) Not Found.
    WARNING: The remote server returned an error: (404) Not Found.
    WARNING: The remote server returned an error: (404) Not Found.
    WARNING: The remote server returned an error: (404) Not Found.
    Unable to find version ‘3.1.0’ of package ‘Common.Logging’.
    Unable to find version ‘3.1.0’ of package ‘Common.Logging.Core’.
    Unable to find version ‘2.2.2’ of package ‘CouchbaseNetClient’.
    Unable to find version ‘6.0.8’ of package ‘Newtonsoft.Json’.

    Do you have any idea what might be going wrong there?

Leave a reply