Pester, Jenkins, Remote & ExitCode


Continuous integration needs your systems and deployments to be totally controlled and tested. Pester is a good framework for that. I’ve already write about it on this blog.

For one of our customer Iโ€™ve worked hand to hand with them on Infrastructure Continuous Delivery in Windows Environment.

I won’t speak about the VMWare, Chef & Jenkins Integration here, Iโ€™ll make another blogpost about it later, but let me share with you what i learned about Pester integration with Jenkins.


As we have deployed our solution and built our server, we are now in the Jenkins Post Build task. In order to be able to execute a script after a build, you’ll need to install this plugin:

You use it, go the the Post-Build Actions section, choose Post build task in the Add post-build action drop down box.

Post build task

The Log text filed is here in order to trigger script regarding what is happening in the log, you can add multiple conditions to build complicated scenarios.

All the console output will be stored in memory in order to parse it, if you want to avoid that, just close the Log text Windows.

Now to get a correct exit code we need to use a switch called –EnableExit available within the Invoke-Pester cmdlet. The problem is that if we want to use Pester remotely to test our targetย  we have few options:

  1. Install Jenkins Slave on target in order to execute script locally -> Maybe the best choice, but my customer didn’t want that solution because it needed new rules on firewall…
  2. Use Invoke-Command -computerName <target> -scriptblock { invoke-command } -> can’t get back the exit code ๐Ÿ™‚
  3. Use the remotely plugin -> the solution we choose.

Another thing is that we want our Pester script to receive arguments from the Jenkins, so at first you’ll need a script to launch the Pester tests.

The script can be something like that to test few stuff regarding an IIS site ๐Ÿ˜‰


Let me explain Invoke-Pester parameters. I need XML outputted file in NUnit XML format in order to put results in Job’s front page. The -script allows me to pass a hash table to Pester with various parameters.

This script has to be on the root of your application folder in your source control management tool. Regarding the Pester tests, you’ll have to put file in a directory called Pester that’ll be committed and available in your Jenkins workplace after. The Pester script will look like this


In order to get remotely module to work, you’ll need WinRM flows opened on your network between Jenkins and the target, and in addition to record target in machineConfig.csv file located at the root of the remotely plugin. To be clear it’s not fully, but the cheat on the script that is running Pester tests is totally good working. Just be sure that the Jenkins service account is in the target’s administrator group and it’ll work.

In the Post build task script use the following command (remove the carriage return) to get the script launched as well as the exit code in order to change the build status if a check is failing.


Do not use the -File parameter of powershell.exe because it won’t return the exit code (in Jenkins)


To finish, add a Post-Build Action called Publish NUnit test result report, and in the XML path, put ../*.XML in order to get all NUnit tests to be printed in root page job.

You now have a totally working remotely Pester tests with results imported in Jenkins. KENAVO !