[HDDS-6496] Improve CI checks

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: build, CI
• Assignee: Attila Doroszlai
• Reporter: Attila Doroszlai
• Created: 23/Mar/22 14:12
• Updated: 17/Apr/24 05:19

Description

Some ideas for improvement:

• compile (11) is not necessary for acceptance test changes, when compilation is necessary only to get the binary tarball for running the tests.
• basic checks are deterministic (except basic (unit) to some degree). Failures can only be fixed by code change, so we can restore fail-fast behavior.
• basic checks are also quick, so we can postpone starting integration until these finish.

Issue Links

• contains: HDDS-5730 Decrease run time of acceptance tests
• is a parent of: HDDS-9000 Speed up unit/integration tests
• relates to: HDDS-5626 Track and Address Flaky tests
• relates to: HDDS-8719 Improve thread names
• relates to: HDDS-6729 Migrate tests to JUnit5

Sub-Tasks

• Add check for dependencies included in Ozone FS shaded jar: Open
• No logs if pod stuck in PodInitializing: Open
• Consistently enable exit-on-error in test scripts: Open
• Enable Gradle remote cache in CI: Open
• Add smoketest in ozone-runner image CI: Open
• Use Java 21 in CI: Patch Available
• Require successful quick checks for repro: Patch Available
• Logs missing if kubernetes check fails before tests: Patch Available
• Reduce duplication in CI workflow: Patch Available