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
Include a binstubs check before running CI script #133
Conversation
return $success | ||
} | ||
|
||
check_binstubs |
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.
Why are you calling this here? The check below in run_build
makes sense but here it seems odd.
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.
o_O copy-paste error
👍 Great idea! LGTM apart from the comment above. |
Newer RSpec contributors may not have setup binstubs. When running `script/run_build` locally it errors in confusing ways. Often at this point they are unsure how to properly get the binstubs onto the system. This includes a very simplistic check for the non-optional binstubs. It aggregates the missing binstubs and the associated gems, then provides the user helpful options on how to get the binstubs. While talking with the users it was decided that this is a kinder approach than simply forcing the creating of the binstubs. Better to inform the user then forcefully inject executables into their system.
5ac0cf8
to
d7c76ac
Compare
Include a binstubs check before running CI script
Looks like this breaks our build :(. |
Looks like rspec-support needs a custom function for this. I'll look into it tomorrow. |
I see why...rspec-support doesn't use cucumber. The check for rspec-dev/travis/script/functions.sh Line 31 in 5098f79
|
NVM this needs a similar check: if [ -d features ]; then |
Updated in #25. Updated the other PRs and will wait for green properly 😬 |
Newer RSpec contributors may not have setup binstubs. When running
script/run_build
locally it errors in confusing ways. Often at thispoint they are unsure how to properly get the binstubs onto the system.
This includes a very simplistic check for the non-optional binstubs. It
aggregates the missing binstubs and the associated gems, then provides
the user helpful options on how to get the binstubs.
While talking with the users it was decided that this is a kinder
approach than simply forcing the creating of the binstubs. Better to
inform the user then forcefully inject executables into their system.