I debated if this message was off topic, but then decided it wasn't, since many of you are, or would like, to be doing the same thing.
I have a Windows Scripting Host (WSH) script that will run a SilkTest script. When it gets done, it sends my custom Silk log file to the QE group along with a summary report of what tests passed/ failed/ did not run.
Silk is on one system (\\SILK), but our builds are done on another system (\\BUILDER). What I would like to do is after the build gets done, have a command run that will execute the script on the Silk system, run the acceptance test, then let us know if it is good or bad via email.
So, both systems are Windows NT 4.0. How can I remotely start this script from the Build system?
333 Moffett Park Drive
Sunnyvale, CA 94089 email@example.com
Ya but what if the developer forgot to check in all the code and the build dies
Thats cool. Since you NT, you probably also have the NT ResKit. On that cd you will find some remote shell utilities. On NT you can run the deamon as a service, then from any win32 client execute rsh <command> <etc>. You could patch that into the end of your make file.
Plus AT is highly unstable, totaly lame and otherwise difficult to use on NT. Also on the ResKit is a WinAT version of AT (GUI front end).
You could also have Silk running, blocking (looping) until a file gets written or a message appears such as 'net send \\silk "Build done, get busy"'