Details

    • Type: Bug
    • Status: Resolved (View workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.0
    • Component/s: None
    • Labels:
      None

      Description

      Exit codes are swallowed up. Ex:

      function run() {
      
        runCommand( 'assertTrue false' );
      
        print.line( 'Finished with success!' );
      
      }
      

      Should the task immediately stop execution when the assertTrue command returns a "failing" exit code of 1? If so, the runCommand method, Command DSL and Task DSL should probably be reworked to actually throw exceptions on a failing status code. That's the only way to have a command automatically fail a task without adding extra plumbing in to capture the exit code and check it every time.

      This bring up other questions such as how do we allow someone to PURPOSEFULLY ignore failing command and just keep executing. Try/catch would be one option. Should there be other ways to do it. Look at bash scripts to see how they handle failing commands.

        Gliffy Diagrams

          Attachments

            Issue links

              Activity

                People

                • Assignee:
                  bradwood Brad Wood
                  Reporter:
                  Gpickin Gavin Pickin
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: