fix: use minimal base image in multi component test by tisutisu · Pull Request #1862 · konflux-ci/e2e-tests

tisutisu · 2026-04-30T16:40:39Z

Description

Using minimal image in the base image, since minimal pipeline is failing while trying to build the image with OOMKilled on upload and sbom-syft-generate steps.

Issue ticket number and link

N/A

Type of change

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

Checklist:

I have performed a self-review of my code
I have commented my code, particularly in hard-to-understand areas
I have made corresponding changes to the documentation
I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
I have updated labels (if needed)

mmorhun

/lgtm

mmorhun · 2026-05-01T06:19:55Z

/retest

mmorhun · 2026-05-01T08:59:18Z

/retest

mmorhun · 2026-05-02T10:59:54Z

/retest

konflux-ci-qe-bot · 2026-05-02T13:36:39Z

Scenario: konflux-e2e
@tisutisu: The following test has Failed, say /retest to rerun failed tests.

PipelineRun Name	Status	Rerun command	Build Log	Test Log
`konflux-e2e-shfmw`	Failed	`/retest`	View Pipeline Log	View Test Logs

Inspecting Test Artifacts

To inspect your test artifacts, follow these steps:

Install ORAS (see the ORAS installation guide).
Download artifacts with the following commands:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-test-storage/konflux-team/e2e-tests:konflux-e2e-shfmw

Test results analysis

🚨 Error occurred while running the E2E tests, list of failed Spec(s):

➡️ [timedout] [It] [disaster-recovery DR Same-Version Backup/Restore] when creating tenants and running initial pipelines should wait for all build PipelineRuns to succeed [disaster-recovery, Serial]

Click to view logs

> Enter [It] should wait for all build PipelineRuns to succeed - /tmp/tmp.QdXROdTIas/tests/disaster-recovery/dr_same_version.go:56 @ 05/02/26 12:53:00.107
STEP: Waiting for per-component build → test chains across all tenants - /tmp/tmp.QdXROdTIas/tests/disaster-recovery/dr_same_version.go:57 @ 05/02/26 12:53:00.107
STEP: Waiting for build PipelineRun for mathwizz-frontend in dr-test-moshekipod-same-version-dr (base: 0) - /tmp/tmp.QdXROdTIas/tests/disaster-recovery/tenant_application_lifecycle.go:163 @ 05/02/26 12:53:00.107
STEP: Waiting for build PipelineRun for mathwizz-frontend in dr-test-kokohazamar-same-version-dr (base: 0) - /tmp/tmp.QdXROdTIas/tests/disaster-recovery/tenant_application_lifecycle.go:163 @ 05/02/26 12:53:00.107
STEP: Waiting for build PipelineRun for mathwizz-web-server in dr-test-moshekipod-same-version-dr (base: 0) - /tmp/tmp.QdXROdTIas/tests/disaster-recovery/tenant_application_lifecycle.go:163 @ 05/02/26 12:53:00.107
STEP: Waiting for build PipelineRun for mathwizz-history-worker in dr-test-kokohazamar-same-version-dr (base: 0) - /tmp/tmp.QdXROdTIas/tests/disaster-recovery/tenant_application_lifecycle.go:163 @ 05/02/26 12:53:00.107
STEP: Waiting for build PipelineRun for mathwizz-web-server in dr-test-kokohazamar-same-version-dr (base: 0) - /tmp/tmp.QdXROdTIas/tests/disaster-recovery/tenant_application_lifecycle.go:163 @ 05/02/26 12:53:00.107
STEP: Waiting for build PipelineRun for mathwizz-history-worker in dr-test-moshekipod-same-version-dr (base: 0) - /tmp/tmp.QdXROdTIas/tests/disaster-recovery/tenant_application_lifecycle.go:163 @ 05/02/26 12:53:00.107
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-same-version-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-same-version-d... the content is too long - please download the artifact to see the full content

➡️ [panicked] [It] [upgrade-suite Create users and check their state] Verify AppStudioProvisionedUser [upgrade-verify]

Click to view logs

runtime error: invalid memory address or nil pointer dereference

➡️ [failed] [It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when a new Component with specified custom branch is created should lead to build PipelineRun finishing successfully [integration-service, github-status-reporting, custom-branch]

Click to view logs

build pipelinerun fails for NameSpace/Application/Component stat-rep-ygxa/integ-app-uaql/test-component-pac-hkkaki with logs: Pipelinerun 'test-component-pac-hkkaki-on-pull-request-hqzkw' didn't succeed

Expected success, but got an error:
    <*errors.errorString | 0xc000942460>: 
    Pipelinerun 'test-component-pac-hkkaki-on-pull-request-hqzkw' didn't succeed
    
    {
        s: "Pipelinerun 'test-component-pac-hkkaki-on-pull-request-hqzkw' didn't succeed\n",
    }

➡️ [failed] [It] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task succeeds when policy is met [ec, pipeline]

Click to view logs

Expected
    : false
to be true

➡️ [failed] [It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for child component [build-service, renovate, multi-component, gitlab]

Click to view logs

Expected success, but got an error:
    <*errors.errorString | 0xc0011a98a0>: 
    
     pod: gl-multi-component-child-xncp-on-pull-request-7r756-init-pod | init container: prepare
    2026/05/02 12:21:43 Entrypoint initialization
    
    pod: gl-multi-component-child-xncp-on-pull-request-7r756-init-pod | container step-init: 
    time="2026-05-02T12:21:47Z" level=info msg="[param] enable: false"
    time="2026-05-02T12:21:47Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128"
    time="2026-05-02T12:21:47Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai"
    time="2026-05-02T12:21:47Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy"
    time="2026-05-02T12:21:47Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy"
    time="2026-05-02T12:21:47Z" level=info msg="Using in-cluster config" logger=KubeClient
    time="2026-05-02T12:21:48Z" level=info msg="Cache proxy is disabled via param"
    time="2026-05-02T12:21:48Z" level=info msg="[result] HTTP PROXY: "
    time="2026-05-02T12:21:48Z" level=info msg="[result] NO PROXY: "
    
     pod: gl-multi-component-child-xncp-on-pull-request-h2wd9-init-pod | init container: prepare
    2026/05/02 12:21:14 Entrypoint initialization
    
    pod: gl-multi-component-child-xncp-on-pull-request-h2wd9-init-pod | container step-init: 
    time="2026-05-02T12:21:18Z" level=info msg="[param] enable: false"
    time="2026-05-02T12:21:18Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128"
    time="2026-05-02T12:21:18Z" level=info msg="[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai"
    time="2026-05-02T12:21:18Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy"
    time="2026-05-02T12:21:18Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy"
    time="2026-05-02T12:21:18Z" level=info msg="Using in-cluster config" logger=KubeClient
    time="2026-05-02T12:21:18Z" level=info msg="Cache proxy is disabled via param"
    time="2026-05-02T12:21:18Z" level=info msg="[result] HTTP PROXY: "
    time="2026-05-02T12:21:18Z" level=info msg="[result] NO PROXY: "
    
    {
        s: "\n pod: gl-multi-component-child-xncp-on-pull-request-7r756-init-pod | init container: prepare\n2026/05/02 12:21:43 Entrypoint initialization\n\npod: gl-multi-component-child-xncp-on-pull-request-7r756-init-pod | container step-init: \ntime=\"2026-05-02T12:21:47Z\" level=info msg=\"[param] enable: false\"\ntime=\"2026-05-02T12:21:47Z\" level=info msg=\"[param] default-http-proxy: squid.caching.svc.cluster.local:3128\"\ntime=\"2026-05-02T12:21:47Z\" level=info msg=\"[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai\"\ntime=\"2026-05-02T12:21:47Z\" level=info msg=\"[param] http-proxy-result-path: /tekton/results/http-proxy\"\ntime=\"2026-05-02T12:21:47Z\" level=info msg=\"[param] no-proxy-result-path: /tekton/results/no-proxy\"\ntime=\"2026-05-02T12:21:47Z\" level=info msg=\"Using in-cluster config\" logger=KubeClient\ntime=\"2026-05-02T12:21:48Z\" level=info msg=\"Cache proxy is disabled via param\"\ntime=\"2026-05-02T12:21:48Z\" level=info msg=\"[result] HTTP PROXY: \"\ntime=\"2026-05-02T12:21:48Z\" level=info msg=\"[result] NO PROXY: \"\n\n pod: gl-multi-component-child-xncp-on-pull-request-h2wd9-init-pod | init container: prepare\n2026/05/02 12:21:14 Entrypoint initialization\n\npod: gl-multi-component-child-xncp-on-pull-request-h2wd9-init-pod | container step-init: \ntime=\"2026-05-02T12:21:18Z\" level=info msg=\"[param] enable: false\"\ntime=\"2026-05-02T12:21:18Z\" level=info msg=\"[param] default-http-proxy: squid.caching.svc.cluster.local:3128\"\ntime=\"2026-05-02T12:21:18Z\" level=info msg=\"[param] default-no-proxy: brew.registry.redhat.io,docker.io,gcr.io,ghcr.io,images.paas.redhat.com,mirror.gcr.io,nvcr.io,quay.io,registry-proxy.engineering.redhat.com,registry.access.redhat.com,registry.ci.openshift.org,registry.fedoraproject.org,registry.redhat.io,registry.stage.redhat.io,vault.habana.ai\"\ntime=\"2026-05-02T12:21:18Z\" level=info msg=\"[param] http-proxy-result-path: /tekton/results/http-proxy\"\ntime=\"2026-05-02T12:21:18Z\" level=info msg=\"[param] no-proxy-result-path: /tekton/results/no-proxy\"\ntime=\"2026-05-02T12:21:18Z\" level=info msg=\"Using in-cluster config\" logger=KubeClient\ntime=\"2026-05-02T12:21:18Z\" level=info msg=\"Cache proxy is disabled via param\"\ntime=\"2026-05-02T12:21:18Z\" level=info msg=\"[result] HTTP PROXY: \"\ntime=\"2026-05-02T12:21:18Z\" level=info msg=\"[result] NO PROXY: \"\n",
    }

➡️ [failed] [It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]

Click to view logs

Timed out after 600.001s.
timed out when waiting for the PipelineRun to start for the component build-e2e-mofp/fj-test-custom-branch-xjdvgc
Expected success, but got an error:
    <*errors.errorString | 0xc0012f42d0>: 
    no pipelinerun found for component fj-test-custom-branch-xjdvgc
    {
        s: "no pipelinerun found for component fj-test-custom-branch-xjdvgc",
    }

➡️ [failed] [It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace should lead to a nudge PR creation for child component [build-service, renovate, multi-component, github]

Click to view logs

Timed out after 1200.000s.
timed out when waiting for component nudge PR to be created in build-nudge-child-tqrpfg repository
Expected
    : false
to be true

OCI Artifact Browser URL

View in Artifact Browser

openshift-ci · 2026-05-05T06:56:47Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mmorhun, psturc

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

~~OWNERS~~ [psturc]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

fix: use minimal image in multi component test

63c9a81

openshift-ci Bot requested review from simonbaird and tnevrlka April 30, 2026 16:40

github-actions Bot added the < 1 min label Apr 30, 2026

tisutisu changed the title ~~fix: use minimal image in multi component test~~ fix: use minimal base image in multi component test Apr 30, 2026

mmorhun approved these changes Apr 30, 2026

View reviewed changes

openshift-ci Bot assigned mmorhun Apr 30, 2026

openshift-ci Bot added the lgtm label Apr 30, 2026

mmorhun added the approved label Apr 30, 2026

tisutisu mentioned this pull request May 5, 2026

feat: move build-service tests to this repo konflux-ci/build-service#586

Merged

psturc approved these changes May 5, 2026

View reviewed changes

psturc merged commit c430de7 into konflux-ci:main May 5, 2026
9 of 11 checks passed

rh-tap-build-team Bot mentioned this pull request May 5, 2026

e2e-tests update konflux-ci/build-definitions#3497

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix: use minimal base image in multi component test#1862

fix: use minimal base image in multi component test#1862
psturc merged 1 commit into
konflux-ci:mainfrom
tisutisu:use-minimal-image

tisutisu commented Apr 30, 2026

Uh oh!

mmorhun left a comment

Uh oh!

mmorhun commented May 1, 2026

Uh oh!

mmorhun commented May 1, 2026

Uh oh!

mmorhun commented May 2, 2026

Uh oh!

konflux-ci-qe-bot commented May 2, 2026

Uh oh!

openshift-ci Bot commented May 5, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Conversation

tisutisu commented Apr 30, 2026

Description

Issue ticket number and link

Type of change

How Has This Been Tested?

Checklist:

Uh oh!

mmorhun left a comment

Choose a reason for hiding this comment

Uh oh!

mmorhun commented May 1, 2026

Uh oh!

mmorhun commented May 1, 2026

Uh oh!

mmorhun commented May 2, 2026

Uh oh!

konflux-ci-qe-bot commented May 2, 2026

Inspecting Test Artifacts

Test results analysis

OCI Artifact Browser URL

Uh oh!

openshift-ci Bot commented May 5, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants