-
Notifications
You must be signed in to change notification settings - Fork 118
feat: implement automated release system for tektoncd projects #3093
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
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]>
fd20080 to
7a53138
Compare
|
/cc @afrittoli @anithapriyanatarajan |
|
@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. DetailsIn response to this:
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 |
There was a problem hiding this comment.
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 😸
There was a problem hiding this 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.
Changes
Adds infrastructure for automated release management of Tekton projects.
Core Components
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 onlyDeployment
automated-releasestekton/resources/kustomization.yamlCloses #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.