Formerly canonical rules for ruby, that are about 2-3 years behind current Bazel. If they work for you great, but if not — please try the new rules ruby by Alex Radionov: https://github.com/bazel-contrib/rules_ruby
Apache License 2.0
99
stars
37
forks
source link
ATTENTION: YOUR OPINION MATTERS S! real world ruby/bazel testers are needed #152
We are trying to decide on which rules should be the primary or canonical rules.
These current rules depend on a very old version of Bazel, fail on CI, but they have been designed with a typical Ruby/rails flow in mind. That's why we have rspec rules and rails example.
The alternative rules by Alex Radionov are much more modern, pass CI across multiple Ruby implementations, provide hermetic build of Ruby, but might be impractical for a large rails application.
I am looking for users of any Ruby rules to play with both and provide some feedback. If Alex's rules become the default, is there anything in this repo that we might want to carry over?
We are trying to decide on which rules should be the primary or canonical rules.
These current rules depend on a very old version of Bazel, fail on CI, but they have been designed with a typical Ruby/rails flow in mind. That's why we have
rspecrules and rails example.The alternative rules by Alex Radionov are much more modern, pass CI across multiple Ruby implementations, provide hermetic build of Ruby, but might be impractical for a large rails application.
I am looking for users of any Ruby rules to play with both and provide some feedback. If Alex's rules become the default, is there anything in this repo that we might want to carry over?