---
title: "Destination reached! | Grafana Labs"
description: "Congratulations on completing the Automate k6 in CI/CD pipelines learning path."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# Destination reached!

Congratulations on completing this learning path! Job well done!

You’ve accomplished the following:

- Learned what CI/CD performance gates are and how exit codes turn k6 thresholds into automated deploy decisions
- Verified that your k6 thresholds produce the correct exit codes for pipeline integration
- Parameterized your script with `__ENV` variables so a single script runs against multiple environments
- Added k6 as an automated step in GitHub Actions or GitLab CI
- Configured your pipeline to treat k6 threshold breaches as build failures that block merges and deployments
- Streamed automated test results to Grafana Cloud k6 for persistent storage and team visibility

### What’s next

k6 is now in the daily workflow. Next, you can extend the gate with environment-specific thresholds, regression tracking, and failure notifications. You can also expand coverage to browser tests and Core Web Vitals.
