Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-27727

Create a way to do a CVE only build in konflux for ACM and MCE

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • ACM 2.16.0
    • Release Management
    • Create a way to do a CVE only build in konflux for ACM and MCE
    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • To Do
    • ACM-23269Konflux Improvements for ACM 2.16
    • Moderate

      Epic Goal

      In CPaaS the build team could perform a z stream release that was simply the previous release with updated images that had no new code changes, but just a base image update.  If code changes were needed, specific components could be updated too.

      To begin discussions on this epic, I talked to Andrew McNamara who confirmed the konflux team will not be adding any features to help in this area.  The suggestion was to investigate working directly with the pipelineruns (Pipelines as Code) and try to get a build to work separately from the main konflux applications and components.  It may be some resources still have to be created to allow the pipelinerun to function.  Running pipelines manually means also creating the snapshot manually.  Our existing release infrastruction may work ok after the snapshot is created.

      Why is this important?

      We need more control than what konflux provides.  Some of this control is nice for CVE only builds.  Some of this control may be nice so developers would not necessarily have to know if a release is frozen or not.  At code cutoff we could freeze the code as a build step but still be able to rebuild the images as needed.

      Scenarios

       

      Acceptance Criteria

      ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. ...

      Open questions:

      1. …

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
        Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub
        Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Doc issue opened with a completed template. Separate doc issue
        opened for any deprecation, removal, or any current known
        issue/troubleshooting removal from the doc, if applicable.
      • Considerations were made for Extended Update Support (EUS)

              Unassigned Unassigned
              gparvin-redhat Gus Parvin
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: