Stop the build if a script fails about heroku-buildpack-run HOT 8 CLOSED

@bigboateng Yes locally, then commit and push as usual.

from heroku-buildpack-run.

oh just read your message above, seems like i need to add: #!/bin/bash line and set the flag

from heroku-buildpack-run.

Hi there,

I just added it. There are also some other changes. You can now specify any types of commands in addition to shell scripts, e.g. binaries and native UNIX commands.

For most users this shouldn't change anything, except that now any shell scripts must be executable, i.e. they must have a #!/bin/bash line and the executable flag set (chmod +x script.sh).

Let me know if the changes work for you.

from heroku-buildpack-run.

The weird thing is that this actually broke deploys for us just now.

-----> Running: ./buildpack-run.sh
/app/tmp/buildpacks/d4963cfdc610c1afed0921a93443e079284fcd2706707c8a33c3d1220c492dbfcb751a745f252dfc67a3828cf1f3cdd01d6bf5d0fc25fa0b511b62c391305643/bin/compile: line 61: ./buildpack-run.sh: Permission denied
-----> Aborting build because './buildpack-run.sh' exited with a non-zero code (126)
 !     Push rejected, failed to compile Run app.
 !     Push failed

We have a script that generates a static.json file and saves it, but for some reason, the latest changes caused a permission denied issue which then quit the whole deploy. I works fine on the last commit before all of your recent changes though.

from heroku-buildpack-run.

Yes, shell scripts are now executed rather than sourced. Thus:

1. #!/bin/bash
2. chmod +x buildscipt-run.sh

from heroku-buildpack-run.

Yes, shell scripts are now executed rather than sourced. Thus:

1. #!/bin/bash
2. chmod +x buildscipt-run.sh

@weibeld where do you run the command chmod +x buildscipt-run.sh? locally?

from heroku-buildpack-run.

@weibeld Perfect, it works now! Thank you very much!

from heroku-buildpack-run.

@vsemionov Great, you're welcome!

from heroku-buildpack-run.