ROX-31183: Use master konflux pipeline to cut a release

[ovalenti]

Description

We have the following intricated situation:

• A Konflux pipeline needs that the branch it is targeting exists
• PRs on a release branch cannot succeed until Konflux builds pass

We propose that the first build on a release branch makes uses of the master Konflux build. Once the first branch build is successful, a PR can be created to point to the new Konflux pipeline (specific to the release branch).

Checklist

• Investigated and inspected CI test results
• Updated documentation accordingly

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 27.38%. Comparing base (f720494) to head (438dd1d).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2833   +/-   ##
=======================================
  Coverage   27.38%   27.38%           
=======================================
  Files          95       95           
  Lines        5427     5427           
  Branches     2548     2548           
=======================================
  Hits         1486     1486           
  Misses       3214     3214           
  Partials      727      727           

Flag	Coverage Δ
collector-unit-tests	27.38% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Molter73]

LGTM!

[tommartensen]

We propose that the first build on a release branch makes uses of the master Konflux build. Once the first branch build is successful, a PR can be created to point to the new Konflux pipeline (specific to the release branch).

That would be the same pattern as we use in stackrox - nothing against this from my side.

[tommartensen]

That would be the same pattern as we use in stackrox - nothing against this from my side.

In fact, there is already a step in the docs to do exactly what you suggest:
https://spaces.redhat.com/spaces/StackRox/pages/690979844/Upstream+Konflux+Release#Upstream%2BKonfluxRelease-update-version-in-reposPutversioninKonfluxpipelines

[ovalenti]

IBM test VMs are failing with a subscription failure, which seems unrelated to the change in this PR.