adoptium / adoptium/aqa-test-tools
Capture openjdk sha in test builds
- Dominant language
- Jupyter Notebook
- Stars
- 33
- Forks
- 97
- Avg merge
- 7h 9m
- Merged PRs (30d)
- 5
Description
According to https://github.com/AdoptOpenJDK/openjdk-build/issues/1476, we can get openjdk sha from the release file. TRSS should capture this information, store it in database, and display it in UI in the tooltip.
Example:
[hotspot](https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-aix-ppc64-hotspot/673/):
`SOURCE=".:git:7c43237a7bde"`
[openj9](https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-aix-ppc64-openj9/736/):
`SOURCE="OpenJDK:e80a3185a3 OpenJ9:04a8b9eb9 OMR:096fcf6da"`
Note: for openj9, the sha info is also in `java -version` output. And we already have code extract them.
Contributor guide
Research direction
Start by reviewing the existing code that extracts OpenJ9 SHA information from java -version output, then trace how release-file data is processed, stored in the database, and shown in the UI tooltip. The work is done when hotspot and OpenJ9 release SHAs, including the listed SOURCE formats, are captured, persisted, and displayed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, database, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100