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

Multiarch CI Improvements and Component Readiness Integration

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • None
    • Multiarch CI Improvements / CR Integration
    • To Do
    • Future Sustainability
    • 25% To Do, 0% In Progress, 75% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • Hide
      • [04 Dec] <DEFERRED> to 4.22
        Pushed out until early 2026 as we don't want a change of responsibility/process at the end of the year.  It'll give everyone more time to adjust at the start of the new year.
      • [20 Nov] <YELLOW> Yellow for 4.21
        There are some changes "in flight" for initiatives in relation to progress here, so we might be deferring some of this to 4.22 development time-frames.  As this is a CI-only change, there is no impact against any given release. (ie `no-feature`)
      • [30 Oct] <GREEN> Green for 4.21
        Pending further discussions within the team, we will be able to plan for adjustments going forward for P/Z.
      Show
      [04 Dec] <DEFERRED> to 4.22 Pushed out until early 2026 as we don't want a change of responsibility/process at the end of the year.  It'll give everyone more time to adjust at the start of the new year. [20 Nov] < YELLOW > Yellow for 4.21 There are some changes "in flight" for initiatives in relation to progress here, so we might be deferring some of this to 4.22 development time-frames.  As this is a CI-only change, there is no impact against any given release. (ie `no-feature`) [30 Oct]  < GREEN > Green  for 4.21 Pending further discussions within the team, we will be able to plan for adjustments going forward for P/Z.
    • None
    • None
    • None

      Epic Goal

      • The multiarch CI signal is valuable for validating our product across all our supported releases.  We would like the multiarch jobs to fall within the default view so regressions can be mitigated through the regular process with the different component teams.

      Why is this important?

      • With the Component Readiness tool being used for regression detection, we will  have consistent regression detection across all supported architectures and platforms.

      Acceptance Criteria

      • All stories filed under the epic are closed.

      Dependencies (internal and external)
      1. Working with the TRT team.

      Done Checklist

      • 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:
              1 Start watching this issue

                Created:
                Updated: