1687a25e39
Having a Rakefile will allow us to change the actual test commands on our side rather than relying on changes to the openstack-infra repository. This should make it a lot faster to change things, but also easier to test since the jenkins jobs are actually run in this repository, not the openstack-infra one. This commit defines the jobs we previously had defined in Jenkins and uses 'high-level' naming consistently (i.e. lint, style vs. foodcritic, rubocop). There is also a :clean task to help with deleting the files generated by the other jobs. Also changed foodcritic to run on the source cookbook rather than the one installed by berks, see e.g. https://github.com/berkshelf/berkshelf/issues/931#issuecomment-29668369 Change-Id: Ia4d52047f1f20b4a62fd1c3726389f3ad562a968 blueprint: rakefile
9 lines
102 B
Plaintext
9 lines
102 B
Plaintext
.bundle/
|
|
berks-cookbooks/
|
|
.kitchen/
|
|
.vagrant/
|
|
.coverage/
|
|
*.swp
|
|
Berksfile.lock
|
|
Gemfile.lock
|
|
Vagrantfile |