Posted: February 11, 2011 05:18 by asayda
I've just started using Hudson (Hudson ver. 1.393) and would like to integrate our test automation with our builds. I am using the 'Execute Windows batch command' option to call a batch file that will start a test application on a remote Windows XP slave. The issue I am having is that the 'exe' that is called is terminated as soon as the batch file finishes execution. I believe the environment that Hudson creates is being cleaned up after finishing the batch file.
Here is the batch file:
start c:\runap.bat BUILD_NUMBER BUILD_VERSION
Is there a way to allow the 'exe' to continue running? In this case the app will run for up to an hour and I don't want Hudson to sit and wait for the app to finish. I've tried calling the app directly (e.g. not through a .bat file) without success. I've been searching several forums without success. Any insight will be greatly appreciated.