Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-6395

[tagRelease.sh] generate openshift release prow config yamls when creating new release-1.y branch

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Critical Critical
    • 1.7.0
    • 1.5.0
    • Build, Quality
    • None
    • RHDH Core Platform 3272, RHDH COPE 3275

      As part of the https://gitlab.cee.redhat.com/rhidp/rhdh/-/blob/rhdh-1-rhel-9/build/scripts/tagRelease.sh script, when branching for 1.6 we should generate new Openshift CI prow config, sorta like this PR:

      https://github.com/openshift/release/pull/62740

      Similar rules to other steps in tagRelease, such that when adding the 1.6 config, we can delete the 1.3 config as it'll be EOL at that point.

      Note that the crontab times will vary by one hour depending on the branch name. https://github.com/openshift/release/pull/63782/files#r2042013704 Need some bit of math to ensure they don't overlap, and they run in the early morning (4am - 8am).

      Due date for this should be when we create the 1.7 branches at feature freeze: Jul 8, 2025.

              joskimca Joseph Kim
              nickboldt Nick Boldt
              RHIDP - Cope
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: