EPIC: Linux Installers - Quality Of Life / Enhancements Tracker

This issue has been raised to track the future enhancements desired for the deb,apk and rpm linux package installers, following the successful implementation of automation in https://github.com/adoptium/installer/issues/1005

FUTURE ENHANCEMENTS:

- [ ] add parameter validations for tag and JDK..
- [ ] For respins during a release, include changelog history ( but reset between releases )
- [x] https://github.com/adoptium/installer/issues/1167
- [x] https://github.com/adoptium/installer/issues/1168
- [ ] Enhance script error reporting for "expected" issues, ie no source ball on github etc.
- [ ] Check out alpine jdk templates for mv src and subpkgdir variable formatting/expansion
- [ ] Document new process.
- [ ] Create Jenkins equivalent of current process to produce linux packages, to be used outside of the release automation
- [ ] #1176
- [ ] Enhance jenkinsfile, by rationalising and improving the architecture ( and similar var ) handling to be consistent.
- [ ] Enhance j2 templates by rationalising and reducing duplication.
- [ ] Allow process to work with a multiple publish, rather than individual tarballs.
- [ ] Add ability to automatically calculate package release number
- [ ] Add process for debian packages to add a new metadata to support a new version
- [ ] Allow package builds for EA/nightly without artifactory publish
- [ ] Rework Github Actions To Check New Process
- [ ] Aim to use podman instead of/as an alternative to docker.
- [ ] Have automated installer job post to slack when successful.

The tracker covers deb, apk and rpm installers, Jenkins, GitHub Actions, Jenkinsfiles and j2 templates. Start by selecting one unchecked enhancement and reviewing the related automation from issue #1005 plus completed issues #1167 and #1168. Done means the selected enhancement is implemented and its package-building process is verified.

Written by the indexing model from the issue text.