Run AIQ Scenarios from Jenkins with Ant
Recommended guidance
Use Jenkins and Ant only when the project still requires an Ant-based automation pipeline. For new pipelines, confirm whether a newer CI/CD approach is available before extending legacy Ant jobs.
Before configuring the job
- Confirm the AIQ environment, project, scenario, and execution target.
- Use service accounts or CI credentials stored in Jenkins credentials management.
- Do not hard-code AIQ usernames, passwords, tokens, or environment secrets in build files.
- Confirm the agent machine can reach AIQ, repositories, browsers, Test Nodes, and required application URLs.
- Keep build files, scripts, and configuration under version control.
Pipeline checks
- Run the Ant target locally or on a controlled Jenkins agent before scheduling it.
- Capture AIQ execution IDs, Jenkins build numbers, logs, and artifacts.
- Fail the Jenkins job when the AIQ result fails, times out, or cannot be retrieved.
- Archive only the evidence required for troubleshooting and compliance.
- Review old Ant jobs periodically and retire duplicate or unused jobs.
Terminology note: Use Scenario Editor when referring to current AIQ scenarios. Keep legacy terms only when describing old job names, file names, or historical assets.
Last updated: October 5, 2026