// LIVE RUNBOOK · CI/CD TEST RESULTS · EXIT-CODE GATING

NexoLoad CI/CD Validation
Runbook

A real validation run using AWS Lambda + API Gateway — smoke testing, forced failure, authenticated endpoint checks, and CI/CD deployment gate confirmation.

📅 Date: May 26, 2026 ☁️ Stack: AWS Lambda + API Gateway (us-east-1) 🛠 Tool: NexoLoad Lite
← Back to CI/CD Guide
Section 1

Overview

This runbook documents an end-to-end NexoLoad CI/CD validation using a dedicated AWS API endpoint. It demonstrates how NexoLoad controls deployment pipelines through raw exit codes — exit 0 continues the deploy, exit 1 stops it.

Purpose
Demonstrate NexoLoad CI/CD gate validation
Stack
AWS Lambda + API Gateway (us-east-1)
API Endpoint
2l5kn7olw2.execute-api.us-east-1.amazonaws.com/prod
AWS Account
205639151494
Tool Used
NexoLoad Lite (macOS binary)
Validated By
BJNexora Solutions · Performance Engineering
Section 2

Validation Scope

  • Deployment validation and readiness verification
  • AWS identity validation
  • Dedicated API endpoint deployment
  • Health endpoint validation
  • NexoLoad Lite smoke test
  • Forced pipeline failure test
  • Authenticated endpoint validation
  • Unauthenticated endpoint (401) check
  • CI/CD gate confirmation
  • SEO and source cleanup verification
Section 3

Commands Used

AWS identity validation:

bashAWS Identity
aws sts get-caller-identity

Health endpoint check:

bashHealth Check
curl -i $API_BASE_URL/health

NexoLoad Lite smoke test:

bashSmoke Test — expects exit 0
./nexoload-lite-mac \ --url $API_BASE_URL/health \ --users 20 \ --duration 10 \ --assert-status 200 \ --raw echo $?

Forced pipeline failure test:

bashFailure Test — expects exit 1
./nexoload-lite-mac \ --url $API_BASE_URL/health \ --users 20 \ --duration 10 \ --assert-status 201 \ --raw echo $?

Authenticated endpoint check:

bashAuth — with Bearer token → 200
curl -i \ -H "Authorization: Bearer $API_TOKEN" \ $API_BASE_URL/api/private

Unauthenticated endpoint check:

bashAuth — no token → 401
curl -i $API_BASE_URL/api/private
Section 4

Actual Results

All tests executed on May 26, 2026 against the dedicated AWS Lambda endpoint.

outputNexoLoad Lite — Smoke Test
NexoLoad Lite · 20 VUs · 10s TPS: 114.7 | P95: 192.0ms | P99: 381.2ms | Errors: 0.0% | Req: 1,167 | Result: PASS Exit code: 0
outputNexoLoad Lite — Forced Failure
NexoLoad Lite · 20 VUs · 10s TPS: 108.7 | P95: 239.0ms | P99: 310.0ms | Errors: 100.0% | Req: 1,113 | Result: FAIL Exit code: 1
Validation Result Notes
Deployment validation complete✓ PASSAll pipeline checks and artifact verifications passed
AWS identity validated✓ PASSAccount 205639151494 confirmed
Dedicated API endpoint deployed✓ PASSAWS Lambda + API Gateway, us-east-1
Health endpoint returns 200✓ PASSGET /health → 200, JSON confirmed
NexoLoad Lite smoke test✓ PASS114.7 TPS · P95 192ms · 0.0% errors · exit 0
Forced pipeline failure works✓ PASS108.7 TPS · 100% errors · exit 1 confirmed
Authenticated endpoint (200)✓ PASSBearer token → HTTP 200 + auth:valid
Unauthenticated endpoint (401)✓ PASSNo token → HTTP 401 Unauthorized
CI/CD gating validated✓ PASSExit 0 = deploy · Exit 1 = block
SEO/source cleanup verified✓ PASSLive site fetch clean, all metadata NexoLoad only
NexoLoad Pro auth test⚠ NOTE--token flag is Pro-only; auth validated via curl
Section 5

CI/CD Gate Explanation

NexoLoad uses raw exit codes for binary pipeline gating. No parsing required — just check the exit code in your pipeline script.

0

Validation Passed

All assertions met. Deployment may continue to the next stage.

1

Validation Failed

Assertions failed or SLA breached. Pipeline stops — deployment is blocked.

yamlGitHub Actions — gate example
# NexoLoad gates deployment on exit code - name: NexoLoad smoke test run: | ./nexoload-lite \ --url ${{ secrets.API_BASE_URL }}/health \ --users 20 --duration 30 \ --assert-status 200 --raw # Exit 1 automatically fails the step and blocks deploy
Section 6

Important Note

Pro Edition — Token Authentication

The Pro authenticated load test requires the --token flag, which is a Pro-only feature. In this validation run, authentication behavior was verified directly with curl, while Lite gate behavior (exit 0 / exit 1) was fully validated using raw exit codes. A NexoLoad Pro license is required to run the full authenticated load test.

Section 7

Deployment Validation

This runbook reflects the current production NexoLoad deployment architecture and CI/CD integration workflow. All validation steps are designed for enterprise-grade execution environments and are repeatable across pipeline runs.

  • Distributed execution verification — confirms all virtual user threads complete within defined SLA thresholds
  • Pipeline integration checks — validates exit code propagation (0 = pass, 1 = fail) across all supported CI platforms
  • Deployment consistency validation — ensures identical behavior across Lite, Pro, and Titan editions in isolated environments
  • Metadata and artifact integrity verification — confirms test output artifacts (JSON, CSV, summary) are well-formed and complete
  • Enterprise deployment readiness checks — validates operation in air-gapped, Kubernetes-based, and regulated network environments
Deployment Targets

The NexoLoad deployment workflow is validated against enterprise CI/CD environments, distributed infrastructure testing scenarios, Kubernetes-based execution clusters, and regulated or isolated deployment environments where outbound internet access is restricted or unavailable.

← Back to CI/CD Guide