Skip to content

Fix: failing jenkins load test jobjob#239

Open
mutambaraf wants to merge 7 commits into
developfrom
fix-failing-jenkins-job
Open

Fix: failing jenkins load test jobjob#239
mutambaraf wants to merge 7 commits into
developfrom
fix-failing-jenkins-job

Conversation

@mutambaraf

Copy link
Copy Markdown
Contributor

Description

Fixed a failing Jenkins job caused by GraphQL schema mismatches (shortCode on Status type) that were crashing teardown and marking k6 pods as failed despite proposals submitting successfully. Hardened run-cluster.sh with set -euo pipefail, trap-based cleanup, and fixed argument parsing. Updated the webpack build to only bundle the test being run and wired graphql-codegen into lint-staged for automatic type regeneration.

Motivation and Context

The deleteProposal and createProposal mutations were sending a field (shortCode) that no longer exists on the Status type in the live schema, causing an uncaught promise rejection in teardown that k6 treated as a fatal error. The shell script had several silent failure modes (no set -e, negative timeout, broken URL argument parser) that masked errors in CI.

How Has This Been Tested

Fixes

Changes

  • run-cluster.sh: fail-fast, trap cleanup, venv activation, fixed arg parser and timeout
  • Jenkinsfile.runcluster: boolean params, env block, aligned defaults with shell script
  • src/graphql/gql/, generated/: removed shortCode from Status selections, regenerated types against live schema, fixed statusId → workflowStatusId
  • webpack.config.js: build only K6_TEST_NAME test, removed target: 'node'
  • package.json, .lintstagedrc.json: auto-run codegen on .graphql file changes

Depends on

Tests included/Docs Updated?

  • I have added tests to cover my changes.
  • All relevant doc has been updated

@mutambaraf mutambaraf marked this pull request as ready for review June 3, 2026 15:42
Comment thread Jenkinsfile.runcluster Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants