Yes, that was what I was suggesting.
If your performance tests need enough consistency that the Jenkins slave
agent growth is a real problem, then it seems like you should consider not
executing the slave on the target node at all. It seems like you may also
want to reboot the computer before sta
Hi Mark,
Thanks for your suggestion. We thought it was convenient to run Jenkins
slave on the machine running the tests because Jenkins would show us the
progress of the job while it is running and other nice to have information.
Are you suggesting that we launch the target program using psex
If you're running performance tests, isn't the presence of any other
processes a risk to the repeatability of your performance test?
Wouldn't it be better to use a Jenkins slave (or master) to launch the
target program from a remote machine, without a Jenkins slave agent on the
machine running th
Two thoughts.
1) When running Jenkins as a service, can you run as a user, instead of
local system? And can you give that user permissions to your share?
2) From a command window, “shutdown /r /t 0” will restart the machine. If
you’re not running as a service you’ll need to log in be
