Partially automate 100% deploy percentage detection
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 7.4k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
With the new json based config builder introduced for Server's updater_server in nextcloud-releases/updater_server#1053 we are closer to being able to more easily detect upstream deploy % changes for the latest major.
We should look at implementing a workflow that detects when the deploy percentage is changed from <100% to trigger bumping our stable and production tags that then, to start, creates either an associated PR for review (with the version change) or, at a minimum, a tracking issue.
P.S. A simpler but similar workflow could be used for automatically detecting maintenance releases (without regard to deploy %).
Related: #2265
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 build/README.md for the JSON-based config builder and review related issue #2265. Define how the workflow detects a deploy percentage changing from below 100% and whether completion means opening a version-bump PR or creating a tracking issue, including the similar maintenance-release case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100