Skip to main content

Link Jenkins Jobs for AIQ Workflows

Link Jenkins Jobs for AIQ Workflows

  • Use explicit parameters between differentjobs jobsinstead of hidden environment assumptions.
  • Fail fast when an upstream job fails or projectsproduces invalid artifacts.
  • Record build URLs and AIQ execution IDs for traceability.
  • Avoid passing secrets through plain-text parameters or logs.

Validation workflow

  1. Define the upstream and downstream job responsibilities.
  2. Pass only required parameters or artifacts.
  3. Run a validation chain in Jenkins.a Fornon-production ourenvironment.
  4. Review learning purposes, we have created two small jobs named ‘Job 01’logs and ‘JobAIQ 02’output inbefore Jenkins server:

    In order to this, let’s go to job 02 and select configure from dropdown:

    Now go to ‘Build triggers’ and select ‘Build after other projects are built’. Under ‘Projects to Watch’ to select ‘job 01’:

    Let’s select ‘Trigger only if build is stable’ so that ‘Job 02’ is executed only when ‘Job 01’ is successfully completed. After this, select save and apply. Now when you build ‘Job 01’ and seeusing the logchain output,for itscheduled should be something like this:


    runs.

    Last updated: JuneSeptember 26,20, 20232026

    If you have any feedback on this topic, please contact us at documentation@appvance.ai