Automate Windows Package Release Process
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 461
- Forks
- 277
- Avg merge
- 16h 48m
- Merged PRs (30d)
- 95
Description
tkn is available via a Chocolatey package, but the process for uploading a new release is manual.
Chocolatey does feature a choco CLI, which offers a choco pack command to build the .nupkg and a choco push command to submit packages for review. Additionally, this would require a Windows image.
The goal here would be to build a Task similar to what we use for other packages, such as rpms.
If doing this for Chocolatey proves challenging, scoop is also an option to look into.
/area release
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading tekton/rpmbuild/rpmbuild.yml to understand how the existing package-release Task is structured. Investigate the Windows image requirement and the choco pack and choco push workflow, with scoop as the stated fallback. Done means a Task can build and submit the Windows package as part of the release process.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100