Skip to content

feat: implement automated release system for tektoncd projects#3093

Draft
vdemeester wants to merge 1 commit intotektoncd:mainfrom
vdemeester:issue-58-automated-releases
Draft

feat: implement automated release system for tektoncd projects#3093
vdemeester wants to merge 1 commit intotektoncd:mainfrom
vdemeester:issue-58-automated-releases

Conversation

@vdemeester
Copy link
Member

@vdemeester vdemeester commented Feb 3, 2026

Changes

Adds infrastructure for automated release management of Tekton projects.

Core Components

  • EventListener with TriggerBindings for release events
  • TriggerTemplates for validation and full release modes
  • scan-release-branches Task - Detects release branches and triggers pipelines
  • release-chatops-router Task - Handles ChatOps commands from GitHub issues
  • manage-release-tracking-issue Task - GitHub issue automation
  • CronJob - Schedules weekly TaskRuns for branch scanning

ChatOps Commands

  • /release-status - Query release PipelineRun status
  • /release-cancel - Cancel running release
  • /release-restart - Restart failed release
  • /release-full - Trigger full release with publishing
  • /release-validate - Run validation only

Deployment

  • Namespace: automated-releases
  • Kustomize overlays for dogfooding environment
  • RBAC and ServiceAccount configuration
  • Wired into parent tekton/resources/kustomization.yaml

Closes #58

/kind feature

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide
for more details.

@tekton-robot tekton-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/feature Categorizes issue or PR as related to a new feature. labels Feb 3, 2026
@tekton-robot tekton-robot requested review from dibyom and wlynch February 3, 2026 15:30
@tekton-robot
Copy link
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 vdemeester 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 needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Feb 3, 2026
Adds infrastructure for automated release management:

Core Components:
- EventListener with TriggerBindings for release events
- TriggerTemplates for validation and full release modes
- scan-release-branches Task to detect release branches and trigger pipelines
- release-chatops-router Task with 5 ChatOps commands
- manage-release-tracking-issue Task for GitHub issue automation
- CronJob that schedules weekly TaskRuns for branch scanning

ChatOps Commands:
- /release-status - Query release PipelineRun status
- /release-cancel - Cancel running release
- /release-restart - Restart failed release
- /release-full - Trigger full release with publishing
- /release-validate - Run validation only

Deployment:
- Namespace: automated-releases
- Kustomize overlays for dogfooding and test environments
- RBAC and ServiceAccount configuration
- Wired into parent tekton/resources/kustomization.yaml

Closes tektoncd#58

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@vdemeester vdemeester force-pushed the issue-58-automated-releases branch from fd20080 to 7a53138 Compare February 3, 2026 15:31
@tekton-robot tekton-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 3, 2026
@vdemeester
Copy link
Member Author

/cc @afrittoli @anithapriyanatarajan
I am going to try to fiddle a bit with it in the dogfooding cluster 👼🏼

@tekton-robot
Copy link
Contributor

@vdemeester: GitHub didn't allow me to request PR reviews from the following users: anithapriyanatarajan.

Note that only tektoncd members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

/cc @afrittoli @anithapriyanatarajan
I am going to try to fiddle a bit with it in the dogfooding cluster 👼🏼

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

kind create cluster --name tekton-test

# 2. Install Tekton
kubectl apply -f https://storage.googleapis.com/tekton-releases/pipeline/latest/release.yaml
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These should be infra.tekton.dev 😸

Copy link
Contributor

@anithapriyanatarajan anithapriyanatarajan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The automation has to pull from latest of oracle cloud buckets.

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

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/feature Categorizes issue or PR as related to a new feature. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Automated release for tektoncd projects

3 participants