Skip to content

ci: add unified CI summary job#182

Merged
tekton-robot merged 1 commit intotektoncd:mainfrom
vdemeester:ci-summary-check
Feb 16, 2026
Merged

ci: add unified CI summary job#182
tekton-robot merged 1 commit intotektoncd:mainfrom
vdemeester:ci-summary-check

Conversation

@vdemeester
Copy link
Copy Markdown
Member

Changes

Add a unified CI summary fan-in job to the CI workflow, ported from
tektoncd/pipeline (38ebfaccd405).

  • Consolidate all CI jobs (build, unit-tests, linting,
    check-licenses, ko-resolve) into a single ci-summary fan-in
    that accepts both "success" and "skipped" as passing states.
  • Prevent docs-only or skipped-job PRs from falsely failing CI.

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
  • Has Tests included if any functionality added or changed
  • pre-commit Passed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

- Consolidate all CI jobs into a single fan-in check that
  accepts both "success" and "skipped" as passing states
- Prevent docs-only or skipped-job PRs from falsely failing

Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
@vdemeester vdemeester added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Feb 16, 2026
@tekton-robot tekton-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Feb 16, 2026
@anithapriyanatarajan
Copy link
Copy Markdown
Contributor

/approve

@tekton-robot
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anithapriyanatarajan

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 [anithapriyanatarajan]

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 approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 16, 2026
@anithapriyanatarajan
Copy link
Copy Markdown
Contributor

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 16, 2026
@tekton-robot tekton-robot merged commit a94b31c into tektoncd:main Feb 16, 2026
20 checks passed
@anithapriyanatarajan
Copy link
Copy Markdown
Contributor

/cherry-pick release-v0.3.x

@tekton-robot
Copy link
Copy Markdown

Cherry-pick to release-v0.3.x failed!

The automatic cherry-pick to release-v0.3.x failed.

Output:

🤖 Starting cherry-pick process...
Fetching PR #182 information...
Found merge commit: a94b31c4140b1610cd5fb67af84a1cab2f216bfa
PR title: ci: add unified CI summary job
Fetching target branch: release-v0.3.x...
From https://github.com/tektoncd/pruner
 * branch            release-v0.3.x -> FETCH_HEAD
Checking for existing cherry-pick PR...
Creating cherry-pick branch: cherry-pick-182-to-release-v0.3.x...
Switched to a new branch 'cherry-pick-182-to-release-v0.3.x'
branch 'cherry-pick-182-to-release-v0.3.x' set up to track 'origin/release-v0.3.x'.
Fetching commits from PR #182...
Found 1 commit(s) to cherry-pick
Cherry-picking commit 1/1: 77653fe02b3e15908cd5e373ff294e7e790dffd8...
fatal: bad object 77653fe02b3e15908cd5e373ff294e7e790dffd8
❌ ERROR: Cherry-pick failed for commit 77653fe02b3e15908cd5e373ff294e7e790dffd8 due to conflicts or other errors

Next steps:

  • Check the action logs for complete details
  • If the PR is not merged, merge it first and try again
  • If there are conflicts, you'll need to manually cherry-pick this PR

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. 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.

3 participants