Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
failing when deployed to secondary machine because "set" in not set t…
…o require
- Loading branch information
e70ad04
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ugh. Travis CI didn't fail on this?
e70ad04
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Never mind, I don't imagine it would. We're not currently testing that the gem builds and installs correctly.
Hrm, I'll create a tracking issue for that. We may be able to do some interesting things with Travis CI.Edit: Never mind, #101 tracks this.
Unrelated: I think you can pull a release from RubyGems with the
yank
command.e70ad04
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks, yanked.
The gem installed fine, but when i went to use it on that machine it crashed.