Content Comparison

...

• Development environment

• Enterprise-scale environment

New Data Center App Performance Toolkit version 8.3.2 with JMeter 5.6.3 support was released.
JMeter 5.6 has a bug which leads to broken .jmx file after opening JMeterUI 5.6.
Also, added pre-run hostname and license validations.Detailed release notes: https://github.com/atlassian/dc-app-performance-toolkit/releases . To get the latest version of the toolkit do git pull on the master branch.How to upgrade virtual env: pip install -r requirements.txt from your virtual env.
How to update docker image: docker pull atlassian/dcapt

Step 1:

For both types of environment need to the same steps as mentioned in the documentation. But while running the below command, if it fails we need to run manually.

...

Note: Need to clear the instances running in the aws environment. Make sure check all the cases like volumes, groups, instances, EKS cluster, RDS database and General purpose buckets.

Step 2:

After pulling the Data Center App Performance Toolkit locally then follow the step 4. Setting up Jira Data Center enterprise-scale environment with "large" dataset. of documentation https://developer.atlassian.com/platform/marketplace/dc-apps-performance-toolkit-user-guide-jira

docker run --pull=always --env-file ./app/util/k8s/aws_envs \
-e REGION=us-east-2 \
-e ENVIRONMENT_NAME=$ENVIRONMENT_NAME \
-v "/$PWD:/data-center-terraform/dc-app-performance-toolkit" \
-v "/$PWD/app/util/k8s/bzt_on_pod.sh:/data-center-terraform/bzt_on_pod.sh" \
-it atlassianlabs/terraform:2.9.1 bash bzt_on_pod.sh jira.yml

Then we need to start execution by Navigate to dc-app-performance-toolkit folder. Before running the command need to add winpty before the command start as shown below

winpty docker run --pull=always --env-file aws_envs \
-v "/$PWD/dcapt.tfvars:/data-center-terraform/conf.tfvars" \
-v "/$PWD/dcapt-snapshots.json:/data-center-terraform/dcapt-snapshots.json" \
-v "/$PWD/logs:/data-center-terraform/logs" \
-it atlassianlabs/terraform:2.9.1 ./install.sh -c conf.tfvars

After running the step 4 of doc then follow step 5.

Need to add the application hostname without ‘http’ and ‘/jira’.

And the same steps need to follow as mentioned in the documentation https://developer.atlassian.com/platform/marketplace/dc-apps-performance-toolkit-user-guide-jira

Before Proceeding Scenario 2: Scalability testing need to prepare the jira.jmx file, for this need to follow the step 3. Develop and test app-specific action locally. Use JMeter app-specific action development example.

Once all the runs completed we need to generate the dependency tree and dependency check report.

• clone the repo

• open command inside the repo folder -- atlas-mvn clean

• atlas-mvn package

After this commands jar and obr file will generate in target folder

• Then go to dependency-check-8.3.1-release\dependency-check\bin path and open command
  dependency-check.bat --scan BulkProfileImporter-1.8.jar --out . --format HTML
  will generate the dependency check report in html

• To get the dependency tree, need to add atlas- before the command
  mvn dependency:tree -DoutputType=dot -DoutputFile=maven_dependency_tree.gv
  
  updated: atlas-mvn dependency:tree -DoutputType=dot -DoutputFile=maven_dependency_tree.gv