From 30e7a408c2b6cd7f5b165773234a75d257bda96c Mon Sep 17 00:00:00 2001
From: Dmytro Yurchenko <dmytro.yurchenko@datadoghq.com>
Date: Thu, 28 Sep 2023 14:06:41 +0200
Subject: [PATCH] Use same BP env vars for pr-commenting and benchmarks jobs

---
 .gitlab/benchmarks.yml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/.gitlab/benchmarks.yml b/.gitlab/benchmarks.yml
index 3620407915f..864d76cb877 100644
--- a/.gitlab/benchmarks.yml
+++ b/.gitlab/benchmarks.yml
@@ -1,6 +1,10 @@
 variables:
   BASE_CI_IMAGE: 486234852809.dkr.ecr.us-east-1.amazonaws.com/ci/benchmarking-platform:dd-trace-js
 
+  # Benchmark's env variables. Modify to tweak benchmark parameters.
+  UNCONFIDENCE_THRESHOLD: "5.0"
+  MD_REPORT_ONLY_CHANGES: "1"
+
 .benchmarks:
   stage: benchmarks
   when: on_success
@@ -18,10 +22,6 @@ variables:
       - platform/artifacts/
     expire_in: 3 months
   variables:
-    # Benchmark's env variables. Modify to tweak benchmark parameters.
-    UNCONFIDENCE_THRESHOLD: "5.0"
-    MD_REPORT_ONLY_CHANGES: "1"
-
     # Gitlab and BP specific env vars. Do not modify.
     KUBERNETES_SERVICE_ACCOUNT_OVERWRITE: dd-trace-js
     FF_USE_LEGACY_KUBERNETES_EXECUTION_STRATEGY: "true"