kudobuilder / kudobuilder/kuttl
Automate Release Process
- Dominant language
- Go
- Stars
- 824
- Forks
- 103
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 6
Description
This should be simple. trigger off version tag and release. MVP is release of kuttl.. but would love to automate:
1. kuttl release
2. docker release
3. krew update (this is the more challenging component as it requires a PR to that repo)
likely want to use github actions... should look at moving to actions for all CI
**What would you like to be added**:
**Why is this needed**:
Contributor guide
Research direction
The issue proposes GitHub Actions automation triggered by a version tag, initially for the kuttl release, with Docker and Krew updates also considered. Start by checking the repository's existing CI and release configuration; done means the tagged-release workflow and the scope of Docker and Krew automation are explicitly resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, go
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100