Uploaded image for project: 'Multiple Architecture Enablement'
  1. Multiple Architecture Enablement
  2. MULTIARCH-4634

Multiarch CI Periodic Migration to Multi Controller

XMLWordPrintable

    • Multiarch CI Periodic Migration
    • 20
    • False
    • None
    • False
    • Not Selected
    • NEW
    • Done
    • ppc64le, s390x, aarch64
    • NEW
    • 0% To Do, 0% In Progress, 100% Done
    • M

      Epic Goal

      • Migrate P/Z/Arm CI jobs to the multi release controller starting with 4.16.

      Why is this important?

      • We're working toward the eventual goal of using the multi-payload by default, where part of this effort is consolidating CI job results into one place for viewing failures and assessing payload quality.

      Scenarios
      1. …

      Acceptance Criteria

      • List of jobs migrated over to the multi release controller.

      Dependencies (internal and external)
      1. …

      Previous Work (Optional):
      1. …

      Open questions::
      1. …

      Done Checklist

      • CI - Job results are consistent on the multi release controller compared to their results on their individual arch release controllers.
      • All the stories, tasks, sub-tasks and bugs that belong to this epic need to have been completed and indicated by a status of 'Done'.

              tvardema Trevor Vardeman
              tvardema Trevor Vardeman
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: