Parameterize the AIQ Controller URL in a GitLab CI/CD Pipeline
Parameterize the AIQ Controller URL in a GitLab CI/CD Pipeline
Parameterize the AIQ Controller URL so the same GitLab CI/CD pipeline can run against different AIQ environments without changing the pipeline script for every deployment.
Recommended approach
- Store the Controller URL as a GitLab CI/CD variable instead of hard-coding it in the pipeline file.
- Use separate variables for development, staging, and production-like AIQ environments.
- Keep authentication tokens and credentials in protected or masked variables.
- Validate the URL before triggering a long-running suite so failed configuration is caught early.
Pipeline checklist
- Define the Controller URL variable in GitLab settings or the pipeline environment.
- Reference the variable from the AIQ execution command or integration script.
- Run a small smoke test to confirm the pipeline reaches the intended controller.
- Review logs to make sure sensitive values are not printed.
- Promote the same pipeline definition across environments by changing only variable values.
Last updated: October 8, 2026