Hello,
I'm curious to know if anyone out there has had experience using VIX to control ANT scripts inside of a Windows XP VM running under VMware Workstation? I'm trying to figure out the right command structure or syntax that can let me execute an ANT script inside the VM from the host OS. This is in support of our build process at work.
Anyway the script xml file is located on the D: drive within the VM, and ant 1.6.5 is installed at D:\ apache-ant-1.6.5. ANT_HOME and all appropriate environment variables are set. Normally when I want to run this script by itself I'd open a command window and type in the following:
D:\ant -f somescript.xml > somescriptlog.txt
This runs the ANT script that pulls code down from our clearcase environment and performs the build. I have yet to figure out a use of the vmrun command that will let me switch the context in the VM to D:/ and then run the script and produce the output file.
In fact the only way I could get this script to run, at all, was to create a bat file and write a vmrun command to call the bat file which then called the script. The only issue I have now is that after the script completes the bat file doesn't die and the Host OS is left waiting for the return. The command I've been using has been:
C:\Program Files\VMware\VMware VIX>vmrun -gu <username> -gp <password> runProgramInGuest "C:\Documents and Settings\All Users\Documents\Virtual Machines\TargetVM\TargetVM.vmx" -ActiveWindow "D:\BuildStart.bat"
So what am I doing wrong? There's got to be some way to call that script directly from the host...does anybody have any other tips?
Also is it just me or does VIX have issues when asking a VM to download data from or copy data up to a maped network drive? Our clearcase repository appears as a networked drive in the VM and the shared folder where we want to output the results is a network drive as well. Both are visible and mounted within the guest and for some reason a script that runs fine when manually triggered within the VM will bomb out when we trigger it using vmrun because it can't find the network drive.
Anyway any light that anyone could shed upon these issues would be greatly appreciated!!!