Skip to content

build(deps): bump github.com/tektoncd/pipeline from 1.9.2 to 1.9.3#1875

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/github.com/tektoncd/pipeline-1.9.3
Open

build(deps): bump github.com/tektoncd/pipeline from 1.9.2 to 1.9.3#1875
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/github.com/tektoncd/pipeline-1.9.3

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github May 22, 2026

Copy link
Copy Markdown
Contributor

Bumps github.com/tektoncd/pipeline from 1.9.2 to 1.9.3.

Release notes

Sourced from github.com/tektoncd/pipeline's releases.

Tekton Pipeline release v1.9.3 "Devon Rex Dreadnought"

-Docs @ v1.9.3 -Examples @ v1.9.3

Installation one-liner

kubectl apply -f https://infra.tekton.dev/tekton-releases/pipeline/previous/v1.9.3/release.yaml

Attestation

The Rekor UUID for this release is 108e9186e8c5677a7943c77b03fff46f83c0876773ae3dcc84e6dcb29d64ca605afb3cbc0ff77ecb

Obtain the attestation:

REKOR_UUID=108e9186e8c5677a7943c77b03fff46f83c0876773ae3dcc84e6dcb29d64ca605afb3cbc0ff77ecb
rekor-cli get --uuid $REKOR_UUID --format json | jq -r .Attestation | jq .

Verify that all container images in the attestation are in the release file:

RELEASE_FILE=https://infra.tekton.dev/tekton-releases/pipeline/previous/v1.9.3/release.yaml
REKOR_UUID=108e9186e8c5677a7943c77b03fff46f83c0876773ae3dcc84e6dcb29d64ca605afb3cbc0ff77ecb
Obtains the list of images with sha from the attestation
REKOR_ATTESTATION_IMAGES=$(rekor-cli get --uuid "$REKOR_UUID" --format json | jq -r .Attestation | jq -r '.subject[]|.name + ":v1.9.3@sha256:" + .digest.sha256')
Download the release file
curl -L "$RELEASE_FILE" > release.yaml
For each image in the attestation, match it to the release file
for image in $REKOR_ATTESTATION_IMAGES; do
printf $image; grep -q $image release.yaml && echo " ===> ok" || echo " ===> no match";
done

Changes

⚠️ Security Fixes

  • GHSA-wjxp-xrpv-xpff / CVE-2026-40161 (HIGH): Git resolver API mode leaks system-configured API token to user-controlled serverURL. A user who can create TaskRuns can exfiltrate the system Git API token by pointing the resolver at an attacker-controlled server.

  • GHSA-94jr-7pqp-xhcq / CVE-2026-40938 (HIGH): Git resolver unsanitized revision parameter enables argument injection. A malicious revision value can inject arbitrary flags into the git CLI, potentially leading to remote code execution on the resolver pod.

  • GHSA-rx35-6rhx-7858 / CVE-2026-40923 (Medium): VolumeMount path restriction bypass via missing filepath normalization. Paths like /tekton/../sensitive bypass the /tekton/ prefix restriction check.

  • GHSA-rmx9-2pp3-xhcr / CVE-2026-25542 (Medium): VerificationPolicy regex pattern bypass via substring matching. Unanchored patterns allow partial matches, letting unsigned resources pass verification.

  • GHSA-m2cx-gpqf-qf74 / CVE-2026-40924 (Medium): HTTP resolver unbounded response body read enables OOM denial of service. A malicious URL returning a very large response can exhaust the resolver pod's memory. Response body is now limited to 1 MiB.

... (truncated)

Changelog

Sourced from github.com/tektoncd/pipeline's changelog.

Tekton Pipeline Releases

Release Frequency

Tekton Pipelines follows the Tekton community [release policy][release-policy] as follows:

  • Versions are numbered according to semantic versioning: vX.Y.Z
  • A new release is produced on a monthly basis
  • Four releases a year are chosen for long term support (LTS). All remaining releases are supported for approximately 1 month (until the next release is produced)
    • LTS releases take place in January, April, July and October every year
    • The first Tekton Pipelines LTS release will be v0.41.0 in October 2022
    • Releases happen towards the middle of the month, between the 13th and the 20th, depending on week-ends and readiness

Tekton Pipelines produces nightly builds, publicly available on gcr.io/tekton-nightly.

Transition Process

Before release v0.41 Tekton Pipelines has worked on the basis of an undocumented support period of four months, which will be maintained for the releases between v0.37 and v0.40.

Release Process

Tekton Pipeline releases are made of YAML manifests and container images. Manifests are published to cloud object-storage as well as [GitHub][tekton-pipeline-releases]. Container images are signed by [Sigstore][sigstore] via [Tekton Chains][tekton-chains]; signatures can be verified through the [public key][chains-public-key] hosted by the Tekton Chains project.

Further documentation available:

  • The Tekton Pipeline [release process][tekton-releases-docs]
  • [Installing Tekton][tekton-installation]
  • Standard for [release notes][release-notes-standards]

Release

v1.12 (LTS)

  • Latest Release: [v1.12.0][v1.12-0] (2026-05-04) ([docs][v1.12-0-docs], [examples][v1.12-0-examples])
  • Initial Release: [v1.12.0][v1.12-0] (2026-05-04)
  • End of Life: 2027-05-04
  • Patch Releases: [v1.12.0][v1.12-0]

v1.9 (LTS)

... (truncated)

Commits
  • 4b778d1 fix: trim whitespace from source URI before pattern matching
  • 87a401f fix: limit HTTP resolver response body size to prevent OOM DoS
  • 34bfa92 fix: strip resolver prefixes and use non-capturing group for pattern anchoring
  • 603644f fix: normalize VolumeMount paths before /tekton/ restriction check
  • bb76e37 fix: prevent git argument injection via revision parameter (GHSA-94jr-7pqp-xhcq)
  • 39e14d4 Security: reject system API token with user-controlled serverURL
  • a26e9c6 Fix running_taskruns metric overcounting TaskRuns with no condition
  • aa0fc1f fix(e2e): replace ubuntu with busybox in dind-sidecar test Dockerfile
  • 64e3723 fix: pin registry image and relax log-based cache assertion
  • 1b37704 fix: bump Go to 1.24.13 to fix CVE-2025-61728, CVE-2025-61726, CVE-2025-61729
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [github.com/tektoncd/pipeline](https://github.com/tektoncd/pipeline) from 1.9.2 to 1.9.3.
- [Release notes](https://github.com/tektoncd/pipeline/releases)
- [Changelog](https://github.com/tektoncd/pipeline/blob/main/releases.md)
- [Commits](tektoncd/pipeline@v1.9.2...v1.9.3)

---
updated-dependencies:
- dependency-name: github.com/tektoncd/pipeline
  dependency-version: 1.9.3
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels May 22, 2026
@openshift-ci openshift-ci Bot requested review from dheerajodha and pmacik May 22, 2026 16:07
@openshift-ci

openshift-ci Bot commented May 22, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign flacatus for approval. For more information see the Code Review Process.

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

Details Needs approval from an approver in each of these files:

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

@konflux-ci-qe-bot

Copy link
Copy Markdown

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

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

Inspecting Test Artifacts

To inspect your test artifacts, follow these steps:

  1. Install ORAS (see the ORAS installation guide).
  2. 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-cbbfz

Test results analysis

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

➡️ [failed] [It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]

Click to view logs

Timed out after 1800.001s.
timed out when waiting for the PipelineRun to start for the component gh-test-custom-branch-hixtgk/build-e2e-jzdv
Expected success, but got an error:
    <*errors.errorString | 0xc000d081c0>: 
    no pipelinerun found for component gh-test-custom-default-qdhgno
    {
        s: "no pipelinerun found for component gh-test-custom-default-qdhgno",
    }

➡️ [timedout] [It] [disaster-recovery DR Suite] DR Backwards-Compat when creating tenants on the old Konflux version 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.GqJgSB5iZp/tests/disaster-recovery/dr_backwards_compat.go:74 @ 05/22/26 18:20:15.733
STEP: Waiting for per-component build → test chains across all tenants - /tmp/tmp.GqJgSB5iZp/tests/disaster-recovery/dr_backwards_compat.go:75 @ 05/22/26 18:20:15.733
STEP: Waiting for build PipelineRun for mathwizz-frontend in dr-test-moshekipod-backwards-compat-dr (base: 0) - /tmp/tmp.GqJgSB5iZp/tests/disaster-recovery/tenant_application_lifecycle.go:196 @ 05/22/26 18:20:15.733
STEP: Waiting for build PipelineRun for mathwizz-frontend in dr-test-kokohazamar-backwards-compat-dr (base: 0) - /tmp/tmp.GqJgSB5iZp/tests/disaster-recovery/tenant_application_lifecycle.go:196 @ 05/22/26 18:20:15.733
STEP: Waiting for build PipelineRun for mathwizz-web-server in dr-test-kokohazamar-backwards-compat-dr (base: 0) - /tmp/tmp.GqJgSB5iZp/tests/disaster-recovery/tenant_application_lifecycle.go:196 @ 05/22/26 18:20:15.733
STEP: Waiting for build PipelineRun for mathwizz-history-worker in dr-test-kokohazamar-backwards-compat-dr (base: 0) - /tmp/tmp.GqJgSB5iZp/tests/disaster-recovery/tenant_application_lifecycle.go:196 @ 05/22/26 18:20:15.733
STEP: Waiting for build PipelineRun for mathwizz-web-server in dr-test-moshekipod-backwards-compat-dr (base: 0) - /tmp/tmp.GqJgSB5iZp/tests/disaster-recovery/tenant_application_lifecycle.go:196 @ 05/22/26 18:20:15.733
STEP: Waiting for build PipelineRun for mathwizz-history-worker in dr-test-moshekipod-backwards-compat-dr (base: 0) - /tmp/tmp.GqJgSB5iZp/tests/disaster-recovery/tenant_application_lifecycle.go:196 @ 05/22/26 18:20:15.733
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-moshekipod-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace dr-test-kokohazamar-backwards-compat-dr: 0/1 build PipelineRuns succeeded
namespace... 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] [enterprise-contract-suite Conforma E2E tests] test creating and signing an image and task verify-enterprise-contract task Release Policy verifies redhat products pass the redhat policy rule collection before release [ec, pipeline]

Click to view logs

Expected
    <[]v1.TaskRunResult | len:1, cap:1>: [
        {
            Name: "TEST_OUTPUT",
            Type: "string",
            Value: {
                Type: "string",
                StringVal: "{\"timestamp\":\"1779470379\",\"namespace\":\"\",\"successes\":405,\"failures\":3,\"warnings\":27,\"result\":\"FAILURE\"}\n",
                ArrayVal: nil,
                ObjectVal: nil,
            },
        },
    ]
not to contain elements
    <[]*tekton.TaskRunResultMatcher | len:1, cap:1>: [
        {
            name: "TEST_OUTPUT",
            jsonPath: "{$.result}",
            value: nil,
            jsonValue: "[\"FAILURE\"]",
            jsonMatcher: <*matchers.MatchJSONMatcher | 0xc0015fd770>{
                JSONToMatch: "[\"FAILURE\"]",
                firstFailurePath: nil,
            },
        },
    ]

➡️ [failed] [It] [konflux-demo-suite] Maven project - Default build when Component is created triggers creation of a PR in the sample repo [konflux, upstream-konflux]

Click to view logs

Timed out after 300.001s.
timed out when waiting for `pull-request` event type PaC PipelineRun to be present in the user namespace "konflux-aouh" for component "konflux-demo-component-fioe" with a label pointing to "konflux-demo-app"
Expected success, but got an error:
    <*errors.errorString | 0xc000700b50>: 
    no pipelinerun found for component konflux-demo-component-fioe
    {
        s: "no pipelinerun found for component konflux-demo-component-fioe",
    }

➡️ [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 | 0xc00241f7c0>: 
    
     pod: gl-multi-component-child-kjdy-on-pull-request-rrrpb-init-pod | init container: prepare
    2026/05/22 17:22:39 Entrypoint initialization
    
    pod: gl-multi-component-child-kjdy-on-pull-request-rrrpb-init-pod | container step-init: 
    time="2026-05-22T17:22:41Z" level=info msg="[param] enable: false"
    time="2026-05-22T17:22:41Z" level=info msg="[param] default-http-proxy: squid.caching.svc.cluster.local:3128"
    time="2026-05-22T17:22:41Z" 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-22T17:22:41Z" level=info msg="[param] http-proxy-result-path: /tekton/results/http-proxy"
    time="2026-05-22T17:22:41Z" level=info msg="[param] no-proxy-result-path: /tekton/results/no-proxy"
    time="2026-05-22T17:22:41Z" level=info msg="Using in-cluster config" logger=KubeClient
    time="2026-05-22T17:22:42Z" level=info msg="Cache proxy is disabled via param"
    time="2026-05-22T17:22:42Z" level=info msg="[result] HTTP PROXY: "
    time="2026-05-22T17:22:42Z" level=info msg="[result] NO PROXY: "
    
    {
        s: "\n pod: gl-multi-component-child-kjdy-on-pull-request-rrrpb-init-pod | init container: prepare\n2026/05/22 17:22:39 Entrypoint initialization\n\npod: gl-multi-component-child-kjdy-on-pull-request-rrrpb-init-pod | container step-init: \ntime=\"2026-05-22T17:22:41Z\" level=info msg=\"[param] enable: false\"\ntime=\"2026-05-22T17:22:41Z\" level=info msg=\"[param] default-http-proxy: squid.caching.svc.cluster.local:3128\"\ntime=\"2026-05-22T17:22:41Z\" 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-22T17:22:41Z\" level=info msg=\"[param] http-proxy-result-path: /tekton/results/http-proxy\"\ntime=\"2026-05-22T17:22:41Z\" level=info msg=\"[param] no-proxy-result-path: /tekton/results/no-proxy\"\ntime=\"2026-05-22T17:22:41Z\" level=info msg=\"Using in-cluster config\" logger=KubeClient\ntime=\"2026-05-22T17:22:42Z\" level=info msg=\"Cache proxy is disabled via param\"\ntime=\"2026-05-22T17:22:42Z\" level=info msg=\"[result] HTTP PROXY: \"\ntime=\"2026-05-22T17:22:42Z\" level=info msg=\"[result] NO PROXY: \"\n",
    }

➡️ [failed] [It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component A triggers a Build PipelineRun for componentA go-component [integration-service, group-snapshot-creation]

Click to view logs

Timed out after 900.001s.
timed out when waiting for the build PipelineRun to start for the componentA group-qhqi/go-component-wupckk
Expected success, but got an error:
    <*errors.errorString | 0xc000446430>: 
    no pipelinerun found for component go-component-wupckk
    {
        s: "no pipelinerun found for component go-component-wupckk",
    }

➡️ [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 does not contain an annotation with a Snapshot Name [integration-service, github-status-reporting, custom-branch]

Click to view logs

Timed out after 900.000s.
timed out when waiting for the build PipelineRun to start for the component stat-rep-gbhe/test-component-pac-ggyrgs
Expected success, but got an error:
    <*errors.errorString | 0xc0010c5210>: 
    no pipelinerun found for component test-component-pac-ggyrgs
    {
        s: "no pipelinerun found for component test-component-pac-ggyrgs",
    }

➡️ [failed] [It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when a new Component with specified custom branch is created the PipelineRun should eventually finish successfully for component [integration-service, gitlab-status-reporting, custom-branch]

Click to view logs

Expected success, but got an error:
    <*errors.errorString | 0xc000815af0>: 
    unable to retrigger pipelinerun for component gitlab-rep-njcr:test-comp-pac-gitlab-wmtpxy: timed out waiting for new PipelineRun to appear after retriggering it for component gitlab-rep-njcr:test-comp-pac-gitlab-wmtpxy
    {
        s: "unable to retrigger pipelinerun for component gitlab-rep-njcr:test-comp-pac-gitlab-wmtpxy: timed out waiting for new PipelineRun to appear after retriggering it for component gitlab-rep-njcr:test-comp-pac-gitlab-wmtpxy",
    }

➡️ [failed] [It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when a new Component is created triggers a build PipelineRun [integration-service]

Click to view logs

Unexpected error:
    : 
    context deadline exceeded
    {}
occurred

➡️ [failed] [It] [build-service-suite Build templates E2E test] HACBS pipelines triggers PipelineRun for symlink component with source URL https://github.com/redhat-appstudio-qe/devfile-sample-python-basic with component name test-symlink-comp-sabd [build, build-templates, HACBS, pipeline-service, pipeline, build-templates-e2e, source-build-e2e]

Click to view logs

Timed out after 1200.001s.
timed out when waiting for the PipelineRun to start for the Component build-e2e-xhfk/test-symlink-comp-sabd
Expected success, but got an error:
    <*errors.errorString | 0xc000b482a0>: 
    no pipelinerun found for component test-symlink-comp-sabd
    {
        s: "no pipelinerun found for component test-symlink-comp-sabd",
    }

➡️ [failed] [It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace triggers a PipelineRun for component go-component-ddpnnh [build-service, github, pac-build, multi-component]

Click to view logs

Timed out after 1800.001s.
timed out when waiting for the PipelineRun to start for the component go-component-ddpnnh/build-e2e-bpwq
Expected success, but got an error:
    <*errors.errorString | 0xc000d0c3c0>: 
    no pipelinerun found for component go-component-ddpnnh
    {
        s: "no pipelinerun found for component go-component-ddpnnh",
    }

➡️ [failed] [It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace triggers a PipelineRun for parent component [build-service, renovate, multi-component, github]

Click to view logs

Timed out after 1941.589s.
timed out when waiting for the PipelineRun to start for the component gh-multi-component-parent-uona/build-e2e-czvl
Expected success, but got an error:
    <*errors.errorString | 0xc0000aabc0>: 
    error listing pipelineruns in build-e2e-czvl namespace: Get "https://api.kx-bed2293a72.4331.p3.openshiftapps.com:443/apis/tekton.dev/v1/namespaces/build-e2e-czvl/pipelineruns?labelSelector=appstudio.openshift.io%2Fapplication%3Dbuild-suite-component-update-ywnn%2Cappstudio.openshift.io%2Fcomponent%3Dgh-multi-component-parent-uona": read tcp 10.128.51.104:52518->54.145.190.69:443: read: connection timed out
    {
        s: "error listing pipelineruns in build-e2e-czvl namespace: Get \"https://api.kx-bed2293a72.4331.p3.openshiftapps.com:443/apis/tekton.dev/v1/namespaces/build-e2e-czvl/pipelineruns?labelSelector=appstudio.openshift.io%2Fapplication%3Dbuild-suite-component-update-ywnn%2Cappstudio.openshift.io%2Fcomponent%3Dgh-multi-component-parent-uona\": read tcp 10.128.51.104:52518->54.145.190.69:443: read: connection timed out",
    }

➡️ [failed] [It] [build-service-suite Build service E2E tests] test git provider fj 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, forgejo]

Click to view logs

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

OCI Artifact Browser URL

View in Artifact Browser

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file go Pull requests that update go code < 1 min

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant