Copy .rubocop.yml into sandbox #55
Conversation
Similar to the copying of `.cane` file, this allows customizing the rubocop ruby style checking rules. At present, the default rubocop rules don't exclude `vendor/bundle` which means when running on travis-ci (and presumably other CI's), rubocop is checking all gems installed from the Gemfile. I'll see about proposing changes to rubocops defaults, but aside from that it would be preferable to also copy across any other customizations
|
@jeremyolliver are you operating on a single cookbook or a chef-repo? |
|
This is operating on a single cookbook repo |
|
@jeremyolliver I'm trying to move people away from Strainer and into a single Rakefile for individual cookbooks. Please see the Jenkins cookbook for an example. |
|
No worries. I'd setup my cookbook using the template provided by https://github.com/paulczar/meez which sets things up via strainer. I'll look at migrating to another solution |
|
Why wasn't this merged? I am using it with chef-repo and it would really be useful. |
|
@soul-rebel please see my previous comment from 2 months ago. |
|
I did and i looked at the changes in jenkins but i am not sure i understand. You recommend against using strainer at all? |
|
@soul-rebel In terms of managing cookbooks, you can either have one git repo with |
|
Yes, as I said, I am using it with chef-repo layout. |
Similar to the copying of
.canefile, this allows customizing the rubocop ruby style checking rules.At present, the default rubocop rules don't exclude
vendor/bundlewhich means when running strainer on my cookbook repo on travis-ci (and presumably other CI's), rubocop is checking all gems installed from the Gemfile. I'll see about proposing changes to rubocops defaults, but aside from that it would be preferable to also copy across any other customizations