Skip to main content

Configure a Parameterized Jenkins Project for AIQ

Configure a Parameterized Jenkins Project for AIQ

Use a parameterized Jenkins project when an AIQ-related automation job needs controlled runtime values such as environment, suite, branch, browser, or execution profile. Keep Jenkins as the orchestration layer and keep AIQ configuration, credentials, and test data in approved locations.

  • Target environment or base URL.
  • Suite, project, or execution profile name.
  • Browser, device, or Test Node group when applicable.
  • Build, branch, or release identifier for traceability.

Good practices

  1. Use clear parameter names and defaults that are safe for non-production execution.
  2. Validate required parameters before starting the job.
  3. Do not store secrets directly in job descriptions, scripts, or documentation.
  4. Record the Jenkins build URL with the related AIQ execution or report.

Last updated: September 8, 2026