Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better failure message for CI apps using default stack #809

Merged
merged 4 commits into from
Sep 14, 2018

Conversation

schneems
Copy link
Contributor

No description provided.

@schneems schneems force-pushed the schneems/heroku-18-bandaid branch from 1424c69 to bf8ca3c Compare September 13, 2018 22:35
@schneems schneems force-pushed the schneems/heroku-18-bandaid branch from bf8ca3c to a358bfa Compare September 13, 2018 22:39
@schneems schneems force-pushed the schneems/heroku-18-bandaid branch from a358bfa to 32ac3ae Compare September 13, 2018 22:41
This test was added to ensure that we didn't accidentally write-over a user's environment variables when we first introduced "user env compile" as a default. It's no longer needed and Rails 4.0 apps cannot install with Ruby 2.4 or 2.5 and that is the only currently available rubies on Heroku 18.
CHANGELOG.md Outdated
@@ -1,5 +1,9 @@
## Master

## v192 (9/14/2018)

* Add error messages when using unsupported Ruby versions on the Heroku 18 stack (https://github.com/heroku/heroku-buildpack-ruby/pull/809)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Heroku-18"

message = <<ERROR
An error occurred while installing #{ruby_version.version_for_download}

This version of Ruby is not available on Heroku 18. The minimum supported version
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Heroku-18"

An error occurred while installing #{ruby_version.version_for_download}

This version of Ruby is not available on Heroku 18. The minimum supported version
of Ruby on the Heroku 18 stack can found at:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Heroku-18"


ci_message = <<ERROR

If you did not intend to build your app for CI on the Heroku 18 stack
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Heroku-18"

mcount "fail.bad_version_fetch.heroku-18.ci"
message << ci_message
else
mcount "fail.bad_version_fetch.heroku-18"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe instead of this add a generic mcount "fail.bad_version_fetch.#{stack}.#{ruby_version.version_for_download}" after this block. That will give us data for future stacks without having to go back and change this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The way we're measuring failures doesn't like reporting the same failure twice under the same key i.e. fail. Otherwise you can end up with failure rates that are higher than 100% we're doing that for version numbers.

@schneems schneems merged commit aa66b72 into master Sep 14, 2018
@edmorley edmorley deleted the schneems/heroku-18-bandaid branch August 27, 2020 06:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants