ci:debug builds

[schneems]

If a part of the build fails before it is ready to run the tests then ci:debug fails. Could we add a flag to drop me into the environment right when where it failed maybe heroku ci:debug --allow-failure. Even better if we could set this via a local environment variable CI_DEBUG_ALLOW_FAILURE=true or something.

I'm trying to debug a customer's app install failing on CI and it takes a good 5 minutes for each iteration.

[gudmundur]

Oh, this is pretty cool. We do have heroku ci:debug --no-setup that allows you to run ci setup manually once you hit bash. I do wonder whether the default behaviour should just do what you're suggesting, rather than kicking you out by default. What do you think of that?

[schneems]

I'm not sure, do we know how many people are using ci:debug ? It's so new, it's probably okay to default to this behavior. Do all the processes of the build happen in the dyno? If so it's totally fine, otherwise anything like writing to a ruby.sh file etc. might not have happened and then the shell won't be helpful to anyone other than buildpack maintainers.

[appleton]

Yes, the builds happen in the dyno too.

As for the ruby.sh concern, we print out some instructions to run source ci env which sources profile scripts etc for you once a build has happened.

[schneems]

I guess i'm talking about the case where the build fails before the buildpack has the opportunity to even write the ruby.sh file. We could re-write the ruby buildpack to stream to that file, but currently we buffer the writes and do it all at once at the end of the build.