XMLWordPrintable

    • Adopt konflux-build-catalog
    • Future Sustainability
    • False
    • Hide

      None

      Show
      None
    • False
    • Green
    • In Progress
    • ACM-23269 - Konflux Improvements (Internal to ACM)
    • ACM-23269Konflux Improvements (Internal to ACM)
    • 0% To Do, 8% In Progress, 92% Done

      Epic Goal

      Every component team adopt https://github.com/stolostron/konflux-build-catalog

      Why is this important?

      The konflux-build-catalog is self-validating. Every PR that modifies a pipeline will trigger the corresponding Konflux build process and EC checks, ensuring that each PR modification works properly. Through GitHub Actions, we have implemented automatic creation of upgrade PRs and automatic merging of PRs when all checks pass. Additionally, for scenarios that require manual migration, messages are sent to the Slack channel to notify responsible parties for timely updates.

       

      Using common pipelines in your project means you delegate the task of updating Konflux task images to konflux-build-catalog, and your repository will no longer see Konflux update PRs.

       

      Adopting it will save. us significant time and effort in maintaining Konflux update PRs.

      1. the Daily Build feasibility mentioned above
      2. 2. whether corresponding pipeline updates should be stopped during code freeze periods, and 3. passing CI_VERSION as build-args to the dockerfile, among others.

      Acceptance Criteria

      All teams adopt konflux-build-catalog

      Dependencies (internal and external)

      1. None

      Open questions:

      1. ???

      Done Checklist

      • tbd

       

      Notes: More details here.

              zxue@redhat.com ZHAO XUE
              tsze@redhat.com To Hung Sze
              Atif Shafi Atif Shafi
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: