I have a bamboo plan to run unit tests on my node.js project. The "Script" task installs my node application and runs the unit tests through "npm run unit-tests". It works great if the Interpreter for my "Script" task is selected as "/bin/sh or cmd.exe".
But recently I added the intelligence in the shell script to pick the right node.js version using nvm. Command: nvm use `cat .nvmrc`.
Since nvm was not recognized in /bin/sh, I changed the interpreter to "Shell" and added "#!/bin/bash" as the first line in my script.
If I run the script from the Ubuntu agent's terminal, the tests run and complete successfully.
However, if I call my npm target (even though the unit tests are successful), the script does not end and move on to the "Final tasks". It is somehow stuck in the same script even though there is nothing to do after that last npm target command.
The bamboo plan finally fails after Hung Build Killer plugin kicks in and stops the plan after 30 mins of inactivity. Can someone explain why the bamboo "Script" task does not gets completed and moves on to the next task?
Environment details:
Ubuntu Agent version: 16.04 LTS (64bit)
Bamboo version: 6.2.2 build 60209
Java version: 1.8.0_151
Node version: v8.9.4
NPM version: 5.6.0
NVM version: 0.31.0
