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: Ie245028db93d6d49eb224747f2c0697c9b6bdcf5
blueprint: rakefile
Removing tailor, cleaning up metadata and Gemfile and adding TESTING.md
Addresses: blueprint rubocop-for-ops-messaging
Change-Id: I4734194aa52973dbaeb299e5970802a38b326dc5
We had two reviews which added an ops-messaging cookbook. Updating
this cookbook with patterns we estabished from the database cookbook.
Craig already did most of the work, however, updated the tests to
use the chefspec find_provider, added clustering support, and attempted
to follow the service_type attribute patterns used in database cookbook.
Since these cookbooks are not complete, added a larger commit than
would have.
Change-Id: I0edfc996df413c6e41a31d53f964d7f5fc9e0aeb