ROX-24276: Enable release builds on Konflux with GOTAGS#13348
ROX-24276: Enable release builds on Konflux with GOTAGS#13348tommartensen merged 1 commit intomasterfrom
Conversation
|
Skipping CI for Draft Pull Request. |
|
Images are ready for the commit at b5a19bd. To use with deploy scripts, first |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #13348 +/- ##
=======================================
Coverage 48.50% 48.50%
=======================================
Files 2470 2470
Lines 178320 178320
=======================================
+ Hits 86487 86492 +5
+ Misses 84900 84896 -4
+ Partials 6933 6932 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
Looks like it worked when testing with the Konflux image locally: That said, shouldn't these changes be made on the release branch instead of master? |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
I think it should be done on both branches for ROX-24276. In the scope of stable and fast stream work, we want Konflux builds to be "release" type builds. The code mentions ROX-20240 for when we intend to use Konflux as a daily-driver as a replacement for GHA (which we won't do now!). That issue is to set the GOTAG depending on whether this is a dev or fast or stable release build. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
|
@tommartensen Would setting Lines 43 to 48 in fa62c32 |
I don't know too much about that mechanism and what (value) BUILD_TAG should be set to... |
|
/test ocp-4-12-scanner-v4-tests |
`MAIN_TAG_SUFFIX` became redundant the moment we start injecting `BUILD_TAG`. Two others, i.e. `COLLECTOR_TAG_SUFFIX` and `SCANNER_TAG_SUFFIX` will be used only when the image flavor is `development_build` and when it's not a release build. We know Konflux builds are release builds since #13348. We also know that Konflux builds will have `rhacs` image flavor and that one relies on the unified tagging, i.e. only `BUILD_TAG` is needed and `COLLECTOR_TAG_SUFFIX` and `SCANNER_TAG_SUFFIX` aren't. I thought it's good to be a bit aggressive removing environment variables because there's a lot of them already and dragging around unused ones is worse than leaving them for the future when we'll be onboarding non-release `development_build`-s on Konflux as a daily driver. Besides, that future might look very differently (e.g. we may want to have unified Dockerfiles).
`MAIN_TAG_SUFFIX` became redundant the moment we start injecting `BUILD_TAG`. Two others, i.e. `COLLECTOR_TAG_SUFFIX` and `SCANNER_TAG_SUFFIX` will be used only when the image flavor is `development_build` and when it's not a release build. We know Konflux builds are release builds since #13348. We also know that Konflux builds will have `rhacs` image flavor and that one relies on the unified tagging, i.e. only `BUILD_TAG` is needed and `COLLECTOR_TAG_SUFFIX` and `SCANNER_TAG_SUFFIX` aren't. I thought it's good to be a bit aggressive removing environment variables because there's a lot of them already and dragging around unused ones is worse than leaving them for the future when we'll be onboarding non-release `development_build`-s on Konflux as a daily driver. Besides, that future might look very differently (e.g. we may want to have unified Dockerfiles).
Description
Enabling the release builds for Konflux builds.
User-facing documentation
Testing and quality
Automated testing
No new tests are required.
How I validated my change
#13348 (comment)