Skip to content

[cherry-pick: release-v0.37.x] fix: use latest Tekton releases and fix ConfigMap timing issue - #3335

Open
divyansh42 wants to merge 1 commit into
tektoncd:release-v0.37.xfrom
divyansh42:cherry-pick-3298-to-release-v0.37.x
Open

divyansh42 wants to merge 1 commit into
tektoncd:release-v0.37.xfrom
divyansh42:cherry-pick-3298-to-release-v0.37.x

Conversation

@divyansh42

@divyansh42 divyansh42 commented Oct 9, 2026 •

Copy link
Copy Markdown
Member

This is a cherry-pick of #3298


Changes

Update E2E test setup to use latest stable releases and fix the Triggers ConfigMap timing issue (test infrastructure only, test/e2e-common.sh).

Pipelines:

  • Use latest release: https://infra.tekton.dev/tekton-releases/pipeline/latest/release.yaml (replaces the storage.googleapis.com URL on this branch; there is no v1.12.0 pin here)

Triggers:

  • Skip nightly builds and use the latest release directly from infra.tekton.dev
  • Fix timing issue: wait for pods AFTER applying interceptors.yaml (not before), so the config-triggers-core-interceptors ConfigMap exists when the controller starts

Submitter Checklist

  • Includes tests (if functionality changed/added) — N/A, test infrastructure change only
  • Run the code checkers with make check — N/A, shell script only (bash -n passes)
  • Regenerate the manpages, docs and go formatting with make generated — N/A, no code changes
  • Commit messages follow commit message best practices

See the contribution guide
for more details.

Release Notes

NONE

Update E2E test setup to use latest stable releases and fix ConfigMap timing issue:

**Pipelines:**
- Remove v1.12.0 pin and use latest release
- Remove TODO comment about switching back to latest

**Triggers:**
- Skip nightly builds and use latest release directly
- Fix timing: wait for pods AFTER applying interceptors (not before)

**Root Cause:**
Triggers v0.37.1 added config-triggers-core-interceptors ConfigMap for GitHub Enterprise allowlist feature. The controller fatally crashes on startup if this ConfigMap doesn't exist, even though the feature defaults to disabled.

Old broken order caused controller to crash:
1. Apply release.yaml (creates controller Deployment)
2. **Wait for pods** (controller starts, needs ConfigMap, crashes)
3. Apply interceptors.yaml (ConfigMap created too late)

**Fix (matching tektoncd/triggers pattern):**
1. Apply release.yaml (creates CRDs and Deployment)
2. Wait for ClusterInterceptor CRD to be Established (provides delay for image pull)
3. Apply interceptors.yaml (creates ConfigMap before controller starts)
4. Wait for pods (controller finds ConfigMap, starts successfully)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
(cherry picked from commit bb65fb6)
@tekton-robot tekton-robot added the release-note-none Denotes a PR that doesnt merit a release note. label Oct 9, 2026
@tekton-robot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please ask for approval from divyansh42 after the PR has been reviewed.

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

@tekton-robot tekton-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Oct 9, 2026
@divyansh42

Copy link
Copy Markdown
Member Author

/retest

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

Labels

release-note-none Denotes a PR that doesnt merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants