Parameterise the way we pass docker images as nodes for test jobs
- Dominant language
- HTML
- Stars
- 155
- Forks
- 346
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 36
Description
At the moment we hardcode certain docker images on which to run tests, such as here https://github.com/adoptium/aqa-tests/blob/67a4672ef525beb1be22a71f547bf91da8e0c4e1/buildenv/jenkins/openjdk_tests#L455.
The plan is to make this procedure better by being able to pass in docker images as parameters to avoid the need to hardcode every desired docker image
Contributor guide
Research direction
Start by reading buildenv/jenkins/openjdk_tests around line 455 and trace how Docker images are currently selected for test jobs. Identify the existing job parameters and configuration flow; the work is done when callers can provide images as parameters without adding hardcoded entries for each desired image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100