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

Shipwright Multiarch Improvements

XMLWordPrintable

    • shipwright-multiarch-improvements
    • Future Sustainability
    • 0% To Do, 0% In Progress, 100% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • Green
    • Hide
      • [2 July] <GREEN> GREEN for 4.19 
      • epic complete
      • [24 June] <GREEN> GREEN for 4.19 
      • blog post PR: https://github.com/shipwright-io/website/pull/170 
      • awaiting review - this is not a priority item for the shipwright team (and was an "extra" item for this effort). They want to release it after v0.16.0 CLI release. Keeping this epic open just to track this issue. 
      • [11 June] <GREEN> GREEN for 4.19 
      • blog post PR: https://github.com/shipwright-io/website/pull/170 
      • awaiting review - this is not a priority item for the shipwright team (and was an "extra" item for this effort). Will be reviewed according to their release schedule
      • [4 June] <GREEN> GREEN for 4.19 
      • blog post PR: https://github.com/shipwright-io/website/pull/170 
      • awaiting review - this is not a priority item for the shipwright team (and was an "extra" item for this effort). Will be reviewed according to their release schedule
      Show
      [2 July] < GREEN > GREEN for 4.19  epic complete [24 June] < GREEN > GREEN for 4.19  blog post PR: https://github.com/shipwright-io/website/pull/170   awaiting review - this is not a priority item for the shipwright team (and was an "extra" item for this effort). They want to release it after v0.16.0 CLI release. Keeping this epic open just to track this issue.  [11 June] < GREEN > GREEN for 4.19  blog post PR: https://github.com/shipwright-io/website/pull/170   awaiting review - this is not a priority item for the shipwright team (and was an "extra" item for this effort). Will be reviewed according to their release schedule [4 June] < GREEN > GREEN for 4.19  blog post PR: https://github.com/shipwright-io/website/pull/170   awaiting review - this is not a priority item for the shipwright team (and was an "extra" item for this effort). Will be reviewed according to their release schedule
    • L

      Epic Goal

      Why is this important?

      • This makes it easier to use shipwright in a multi-arch compute environment by adding features such as NodeSelectors and Tolerations that didn't previously exist. 

      Scenarios
      1. …

      Acceptance Criteria

      • (Enter a list of Acceptance Criteria unique to the Epic)
      • …

      Dependencies (internal and external)
      1. …

      Previous Work (Optional):
      1. continuation of shipwright work done in https://issues.redhat.com/browse/MULTIARCH-4665

      Open questions::
      1. …

      Done Checklist

      • CI - For new features (non-enablement), existing Multi-Arch CI jobs are not broken by the Epic
      • Release Enablement: <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR orf GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - If the Epic is adding a new stream, downstream build attached to advisory: <link to errata>
      • QE - Test plans in Test Plan tracking software (e.g. Polarion, RQM, etc.): <link or reference to the Test Plan>
      • QE - Automated tests merged: <link or reference to automated tests>
      • QE - QE to verify documentation when testing
      • DOC - Downstream documentation merged: <link to meaningful PR>
      • 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'.

              dorzel Dylan Orzel
              dorzel Dylan Orzel
              Brian Cogan
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: