Why does Heroku continue to deploy, even if rake assets: does precompilation fail?

Question

When deployed to heroku, heroku continues to deploy even if rake assets: precompilers do not work.

Why is this the default behavior? Is there a way to prevent the hero from deploying the version if rake assets: precompilation fails? Thanks.

-----> Writing config/database.yml to read from DATABASE_URL -----> Preparing app for Rails asset pipeline Running: rake assets:precompile rake aborted! The line was indented 2 levels deeper than the previous line. (in /tmp/build_3tgkcip2wq2qv/app/assets/stylesheets/master.css.sass) Tasks: TOP => assets:precompile:primary (See full trace by running task with --trace) Precompiling assets failed, enabling runtime asset compilation Injecting rails31_enable_runtime_asset_compilation Please see this article for troubleshooting help: http://devcenter.heroku.com/articles/rails31_heroku_cedar#troubleshooting -----> Rails plugin injection Injecting rails_log_stdout Injecting rails3_serve_static_assets -----> Discovering process types Procfile declares types -> (none) Default types for Ruby/Rails -> console, rake, web, worker -----> Compiled slug size is 52.9MB -----> Launching... done, v163 

Answer 1

Because even if the asset compilation fails, the application will be able to serve requests that do not include assets, fx serving REST xml or json requests.