How to setup Jagger locally or on the CI environment

Local installation

Requirements: java, maven, docker

In general all Jagger components for local installation can be separated to:

Results storage and representation components
Load generating components

To install and launch Result storage and presentation components you can use docker

Download docker compose .yml file for local installation compose-2.0-package.zip from https://nexus.griddynamics.net/nexus/content/repositories/jagger-releases/com/griddynamics/jagger/compose/2.0/ and unzip it

Run docker compose. All necessary images will be downloaded from the DockerHub and launched locally in containers

docker-compose -f docker-compose.yml up

More details on docker compose setup in the readme.txt

After the installation you will get following components running as docker containers:

MySQL database for test results storage
Jagger WebUi for results representation, comparison, sharing. By default http://localhost:8087/
MySQL database for Jagger as a Service (JaaS) configuration
JaaS REST API. By default at http://localhost:8088/jaas/swagger-ui.html#/

To install and use Load generating components we are creating a Jagger test project from template

Create new test project from template

mvn archetype:generate -DarchetypeGroupId=com.griddynamics.jagger -DarchetypeArtifactId=jagger-archetype-java-builders -DarchetypeVersion=2.0 -DarchetypeRepository=https://nexus.griddynamics.net/nexus/content/repositories/jagger-releases/

Note: Latest version number archetypeVersion you can find in Release notes

Maven will ask you to enter groupId, artifactId, version and package name.

After the installation you will get following components:

Java maven project with artifactId name. Project will contain examples of the performance tests

How to run the project and write you first test - Run test project

CI installation

NOTE It is advanced section dedicated to the framework intergation to CI. If you are the first time here, you can skip it for now and return to it later

Framework is suitable for execution in the CI pipelines. It allows to build Continuous Performance Testing. You can read: