Jenkins File Reference for AIQ Integrations

Last reviewed: September 24, 2026

Use this page to explain what the Jenkins files are for when AIQ test execution is triggered or coordinated from a CI pipeline.

What changed in this article

• Clarify which files define build parameters, which call AIQ, and which publish or collect results.
• Keep customer-specific job names, tokens, and workspace paths out of the shared documentation.
• Point users to the Jenkins job configuration article when they need step-by-step pipeline setup.

Validation workflow

1. Identify the Jenkinsfile or helper script used by the project.
2. Confirm required parameters such as AIQ project, scenario, environment, and result handling.
3. Run the job in a non-production folder before adopting it for scheduled execution.

Review note: Made the article a file-purpose reference instead of a loose Jenkins note, so it fits with the Jenkins integration pages.

Last updated: September 24, 2026

If you have feedback on this topic, contact documentation@appvance.ai.