cli doesn't return exit code from publish (angular)

[solshark]

Describe the bug
amplify publish (for angular project) doesnt pass back exit code from ng build.
I was trying to setup CI/CD with gitlab and docker executioner. I used image with no angular cli installed for test purposes and spotted following issue:

> [email protected] build /builds/trinity/jumbo
> ng build

sh: ng: not found
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! [email protected] build: `ng build`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-11-22T10_59_12_859Z-debug.log
frontend build command exited with code 1
$ echo $?
0

Even if ng build failed amplify still returned exit code 0 which leads to CI jobs being marked as successfully completed.

Amplify CLI Version
3.17.0

Expected behavior
Return proper exit code.

Desktop (please complete the following information):

• OS: Debian
• Node 12-alpine

[github-actions]

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.