Add a script to run Jepsen tests

One can use tests as a JAR file as below:

$ java -jar target/jepsen.tarantool-0.1.0-standalone.jar
Usage: lein run -- COMMAND [OPTIONS ...]
Commands: analyze, serve, test, test-all

However it is not convenient to write `java -jar ...` each time,
so shell script `run-jepsen` was added that do it for you.

$ ./run-jepsen
Usage: run-jepsen test --help
$ ./run-jepsen test --username root --nodes-file nodes --workload register

Related to #97

Author: ligurio

.github/workflows/publish.yml

@@ -33,6 +33,7 @@ jobs:
         lein uberjar
         zip jepsen.tarantool-${{ env.TAG }}.zip
             target/jepsen.tarantool-${{ env.TAG }}-standalone.jar
+            run-jepsen
             README.md
             CHANGELOG.md
 

CHANGELOG.md

@@ -61,3 +61,4 @@ change log follows the conventions of
 - Add primary node discovery (#43, #17).
 - Add bank workload (#67).
 - Enable uberjar support and build JAR file in CI.
+- Add shell script for running Jepsen tests.

run-jepsen

@@ -0,0 +1,26 @@
+#!/bin/sh
+
+set -eu
+
+release_version="0.1.0"
+
+test_options=$@
+if test -z "$test_options"; then
+    echo "Usage: $(basename "$0") test --help"
+    exit 0
+fi
+
+jar_path="./target/jepsen.tarantool-${release_version}-standalone.jar"
+if [ ! -f "$jar_path" ]; then
+    echo "JAR file ($jar_path) is not found!"
+    exit 1
+fi
+
+java_path=$(readlink -f $(which java))
+if test -z "$java_path"; then
+    echo "No Java binary found."
+    exit 1
+fi
+
+cmd_line="$java_path -jar $jar_path $test_options"
+eval $cmd_line