How to check/track what has been completed as part of a release / ensure nothing is missed.
- Dominant language
- Jinja
- Stars
- 168
- Forks
- 77
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 12
Description
As part of a release cycle, the JDK release binaries are pushed to github.
This process then triggers an automated job to create the following files:
- APK linux installer packages for Alpine Linux
- DEB linux installer packages for various Ubuntu Linux distributions & versions
- RPM linux installer packages for both various RHEL & SUSE based Linux distributions & version.
Currently the only way to check if all the correct packages have been created, and uploaded to artifactory is to log in to artifactory and check that all the relevant files are in place.
It would be good to automate this check/report.
Contributor guide
Research direction
Start by tracing the automated job triggered when JDK release binaries are pushed to GitHub. Review how APK, DEB, and RPM packages are produced and uploaded to Artifactory. Done should include an automated check or report showing whether all relevant packages for the release are present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100