echo "VMWare version did not match, expected release ??TARGET.DT.VMWARE_RELEASE??"

echo "Actual version ${VMWARE_INSTALLED}"

exit 1

else

echo "VMWare PASSED"

exit 0

fi

}

I want the BLPackage to run through each ext command and if the version is incorrect, to throw out an error and continue parsing the next Ext Command.

For each ext. command, I set the ActionOnFailure to COntinue, and added the exit 1 and exit 0 codes (in bold above) to the script.

When I run the package, it comes back successful, even though the logs show that the versions are incorrect, but my BLpackage job never fails, so the user running the job from bladelogic has no idea that the versions are incorrect and doesnt see any errors.

is there any way to make the BL job error out and continue parsing the rest of the external commands? The 'exit 1' code doesnt seem to make it error out, the job completes with a green check mark.

Ok I got it to work. Is there any way to make it throw out an warning instead of an error, in other words I want the BLpacakge deploy job to finish with a warning, and not just error out, and is there a way write a custom warning message for example

Job Run: BLPackage deploy - Python version check

>Warning: installed python version does not match the required version of 2.5.6

Right now I can get it to error out with this message, which isnt too descriptive