Powershell plugin adding 5 minutes to build?

[Kyle Howard]

I’m using Jenkins with TFS and MSBuild, and we’re using Nunit for testing.

 

I’ve written a Powershell script to find unit test DLLS then pass them to the nunit-console command one at a time.  We’re running only about 50 tests, and this is working just fine when I run the PS script at a command line.  The average time to finish all of the tests is about 30 seconds.

 

When I add the Powershell plugin into Jenkins and have Jenkins run the same script, nunit reports the exact same 30 seconds for running the tests, but Jenkins seems to hang for almost exactly 5 minutes during the test phase of the build, this triples our build time and is causing my devs to get grumpy.

 

Has anybody run into this before?  I don’t feel like I’m doing anything special here…

 

Kyle Howard

Gila LLC

m: 512-294-1067

Configuration Manager

 

[Tim Hargreaves]

Are you running the Log Parser plugin? Are the tests/PowerShell the last step before the parser? Is the log output large?

I had a similar situation where it looked like XCode was hanging the build doing nothing, when it was actually the log parser running, but since it doesn't generate any output when it starts, it looks like whatever the previous build step is is blocking the job.

When you say you're running it on the command line and it's fine, is that running it on the same node, or on your personal machine?

Tim

[Tim Hargreaves]

Only other suggestion I have then is to add a regular command window and run `powershell myscript.ps1` and see if that has the same delay. We're using Mac nodes, so I don't have too much experience with the PS plugin.

Good luck!

On Thu, Oct 15, 2015 at 9:37 AM, Kyle Howard <kyle....@gilacorp.com> wrote:

I’m running it on the same node in a powershell window, then copying the code and pasting it into the Jenkins powershell script plugin, and I’m not using the Log Parser plugin at all so far, but it looks like that might be useful.