CI build Process Required about caliper HOT 2 CLOSED

Have started working on this, the proposal is to:

• Use Travis (I have more experience setting up/using this CI environment, and it is great for OS projects such as Caliper 👍 )
• add a pretest package command that runs the lint checker
• Use the existing npm test command
• Run multiple environments, one per available benchmark, using the npm test --<benchmark>

The above will ensure that:

• No linting regressions creep in
• All published benchmarks (local only) will not regress

from caliper.

Currently have a working (local) Travis CI system in place which is running each benchmark contained in the project. Each benchmark runs in a separate environment, and the scripting is configured to run a benchmark with a target version. It has been proven to fail-out correctly (required files missing, no benchmark, test failure etc)

The framework runs the e2e tests as started by test.js within the scripts folder.

Once the initial drop of the linting checking has been made, I will incorporate the lint checker into the pretest section so that it is run before the main regression check.

I have not yet considered the running of the zookeeper based functionality as part of the regression suite

from caliper.