VilnaCRM-Org/crm-infrastructure

Fix CRM load test setup path drift in ci-cd pipeline

Open

#28 opened on Mar 13, 2026

View on GitHub
 (1 comment) (1 reaction) (0 assignees)HCL (0 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (0 stars)
PR merge metrics
 (PR metrics pending)

Description

Summary

ci-cd-crm fails in the loadTests batch on main because the infrastructure repo still prepares k6 config under crm/src/test/load, while the CRM repository stores load-test assets under crm/tests/load.

Evidence

  • Prod pipeline: ci-cd-crm-prod-pipeline
  • Execution: 4af664ae-5b20-4200-9fb5-82d8ec02e26f
  • Failed child build: ci-cd-crm-prod-batch-pw-load:b63740b0-974f-40e9-ab71-b962641e8d9b
  • Infra script: aws/scripts/sh/k6_installation.sh
  • Current incorrect paths:
    • crm/src/test/load/config.json.dist
    • crm/src/test/load/config.json
  • Actual CRM repository paths:
    • crm/tests/load/config.json.dist
    • crm/tests/load/...

Expected

  • k6_installation.sh should prepare load-test config from the actual CRM repository layout.
  • ci-cd-crm should pass on test and prod from main.

Acceptance criteria

  • aws/scripts/sh/k6_installation.sh handles the CRM load-test directory correctly
  • GitHub CI is green
  • CodeRabbit approves the PR
  • ci-cd-crm-test-pipeline succeeds from main
  • ci-cd-crm-prod-pipeline succeeds from main

Contributor guide

Research direction
Inspect the script aws/scripts/sh/k6 installation.sh and update the paths from crm/src/test/load to crm/tests/load to match the CRM repository layout.
Tech stack
shell
Domain
ci cdinfrastructure
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75