Pipeline Flow

Adapted from the Jenkins QA deployment guide to show how master and agents handle presets and updates.

Overview

  • Master schedules deployments of service presets to QA machines running inbound agents.

  • Presets create per-service folders with data, logs, and configs.

  • Updates pull new images while keeping on-host customizations intact.

  • Functional details of steps and templates live in the shared library docs (see link below).

Architecture

qa-architecture

Deployment Sequence

deployment-sequence

Directory Structure on QA Machine

<preset-name>/
  <service-1>/
    data/
    logs/
    configs/
  mysql/
    data/
    logs/
    configs/
  acs/
    config/
    log/
  <service-2>/
    data/
    logs/
    configs/

Updates and Persistence

  • Customizations on disk remain when updating images.

  • Safe update pattern:

    • Pull new image.

    • Stop container.

    • Start container with same mounted volumes; custom files stay.

Key Benefits

  • Quick QA machine enablement via inbound agent.

  • Safe updates without losing local customizations.

  • Organized, per-service preset layout.

  • Multiple presets can coexist on one machine.

See Also

  • Functional capabilities of master/agent pipelines and templates: see shared library docs at ../ft-qa-shared/docs/modules/ROOT/pages/index.adoc.