Fail integration tests appropriately

[dbeatty10]

Closes #540

This is a:

• bug fix PR with no breaking changes

Description & motivation

The integration tests passed in CircleCI even though one of the dbt steps failed. This is because the shell script only returns the final exit code -- intermediate exit codes are ignored by default.

Several options to solve this issue are discussed here.

Chosen option: command || exit 1 because it is minimally invasive, low risk, and preserves our optionality in the future.

Positive Consequences

• solves the immediate problem
• low risk
• minimally invasive and straight-forward
  • only requires adding the || exit 1 suffix to 5 lines of code
• preserves our optionality in the future
  • completely reversible
  • doesn't prevent us from pursuing the other ideas like dbt build, etc as the next logical steps to take
• inspiration to learn more how bash behaves

Negative Consequences

• raises question if this solution should be advocated for every other project that uses something like a run_test.sh script
• harder to read for those of us not expert in bash

Checklist

• I have verified that these changes work locally on the following warehouses (Note: it's okay if you do not have access to all warehouses, this helps us understand what has been covered)
  • BigQuery
  • Postgres
  • Redshift
  • Snowflake
• I followed guidelines to ensure that my changes will work on "non-core" adapters by:
  • dispatching any new macro(s) so non-core adapters can also use them (e.g. the star() source)
  • using the limit_zero() macro in place of the literal string: limit 0
  • using dbt_utils.type_* macros instead of explicit datatypes (e.g. dbt_utils.type_timestamp() instead of TIMESTAMP
• I have updated the README.md (if applicable)
• I have added tests & descriptions to my models (and macros if applicable)
• I have added an entry to CHANGELOG.md

[jasnonaz]

Looks great - thanks for fixing this!