Resolve "Improve Release CI"
Closes #179 (closed)
It will be a little tough to verify the changes have an effect for the download links because they must be merged/integrated into the upstream default branch for them to take effect. I've verified this on my fork and things work as expected.
I've organized the package (JAR) with the hierarchy: CLIENT_VERSION/CI_JOB_ID
. This quickly identifies which version of the JAR the user might download and the JOB ID is a simple build number. Additionally, the GitLab interface automatically provides the build date/time as well as the branch/tag (ref) from which the JAR was built.
I'm open to ideas for other organization structure. We are somewhat limited by the GitLab generic package registry API: https://docs.gitlab.com/ee/user/packages/generic_packages/#publish-a-package-file
Example Display: