- Switched default linter to cookstyle
- Renamed rake tasks to better conform with Chef conventions
Change-Id: If9ef1641600ca2d4bea1e3b538304dd2f1d3651f
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: Id085444027efd90049508abe6a309fed7dfffee8
blueprint: rakefile
This first pass gets tempest installed to /opt/tempest, and sets up
necessary users for testing. More work needs to be done on adding
correct configuration to tempest.conf and enabling different features
depending on what exists in the environment. This will most likely
involve exposing everything via different attributes.
Since we checkout master of tempest, the cookbook assumes tempest
will be executed to use a virtual env. This will hopefully safe-guard
us from future package-related issues. Note that at the moment
the python virtual env does NOT build cleanly on RHEL 6.5. According
to devstack, it appears that a number of work-arounds are required to
make tempest run on RHEL 6.5.
Change-Id: I08224d2f4784d2fc041a5806f221e7411d5b813a
Ghanshyam Mann