1 Reply Latest reply on Jul 12, 2011 11:10 AM by Bill Robinson

    Custom Software deploy with non-standard exit code

      We are working to deploy custom software using BBSA 8.1


      When we execute the deploy job it runs fine and actually installs the software we have. The problem is that our install exits with a non-standard exit code of 200 (instead of 0)


      When BBSA receives the 200 exit code it assumes an error occurs and shows the job as failed... even though it succeeded and the software is actually installed.


      Is there anyway to tell BBSA that the exit code 200 for this specific software, or deploy job, signals a successful install?


      If we have to we can force our software to return 0 but it would be much better if we can use the exit code built into our custom software from the beginning.