Rather than suggest editing the bootstrap scripts we should recommend
setting environment variables to point to existing Erlang installations,
if present.
Also updated the build versions to 2.0.0rc1 and 1.4.10
* Checks the list of stats keys returned from the HTTP endpoint
is complete -- delineating between riak and riak_ee. The test will
fail if the list returned from the HTTP endpoint does not exactly match
the expected list. This behavior acts as a forcing function to ensure
that the expected list is properly maintained as stats are added and
removed.
* Modifies reset-current-env to properly clean dependencies when a
full clean is requested and remove the current directory in the
target test instance.
* Adds logging to verify_riak_stats to explain the addition steps
being performed
* Adds rt:product/1 to determine whether a node is running riak,
riak_ee, or riak_cs
* Adds tools.mk support and eunit scaffolding to rebar.config
* Modifies reset-current-env.sh to remove the current directory in
the target test instance
AAE is disabled. (defect https://github.com/basho/riak_kv/issues/959)
- Adds additional console output to reset-current-env to explain
configuration and steps being executed
- Adds the -n option to the reset-current-env script to specify the
number of nodes to build. By default, 5 will be created.
an undefined bucket type is specified. (defect #875)
- Adds a description of the reset-current-env.sh script and its
usage to README.md
- Corrects a spelling mistake in an information message emitted by
the reset-current-env.sh script
This change allows initialization of ~/rt/riak to proceed even if
releases aren't built, or if you run this script outside of your
test-releases directory. It will report this to the user however.
This is useful if you only want to run riak tests against current. New
users of riak test and people working on bugs on crazy branches will
especially want this since they likely do not want to take the time to
build multiple releases that may not even be relevant to the bug.
