Dynamic compilation - auto detect BUILD_LIST based on TARGET
- Dominant language
- Java
- Stars
- 22
- Forks
- 114
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 8
Description
It would be nice if we can auto-detect `BUILD_LIST` value based on `TARGET`. It means that `BUILD_LIST` will be an optional value. Similar to `JDK_VERSION`. The goal is to further reduce test build running time in Grinder and [comment triggered PR builds](https://github.com/AdoptOpenJDK/openjdk-tests/pull/2222) and to make our test framework more user friendly.
Part 1: clean up cmdlinetest tests that need multiple folders in BUILD_LIST
For example, cmdlinetests need 3 folders:
```
BUILD_LIST=functional/cmdline_options_tester,functional/cmdline_options_testresources,functional/cmdLineTests/jvmtitests
```
Part 2: clean up dependencies in rest of functional tests
Part 3: add feature in TKG to generate BUILD_LIST based on BUILD_LIST and target
Part 4: clean up dependencies in other repos
Contributor guide
Research direction
Start by tracing how TKG currently consumes BUILD_LIST, TARGET, and JDK_VERSION, then review the cmdlinetest tests and their listed folders. Determine how each of the four parts depends on the existing build configuration; done means BUILD_LIST can be omitted and is generated correctly without breaking the referenced functional tests or other repositories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100