Aias00 opened a new pull request, #4119: URL: https://github.com/apache/hertzbeat/pull/4119
## What's changed? This first-stage CI optimization pass keeps the existing workflow coverage intact, but reduces repeated setup work and duplicate compute: - cache Maven dependencies in the shared Java setup action - cache the downloaded `mvnd` distribution in the shared Java setup action - add `concurrency` to cancel superseded workflow runs for the same branch/PR - add pnpm cache setup for frontend/docs workflows - remove duplicated nightly Maven rebuild steps while preserving the release and collector-cluster packaging flow ## Expected benefits Current workflow history shows the heavier pipelines still spend a noticeable amount of time in repeated setup and duplicate work: - `Backend CI` recent runs include `13m49s` and `14m33s` - `Frontend CI` recent runs include `7m31s` - `DOC CI` recent runs include `10m38s` This PR should improve CI in three ways: - reduce warm-run latency for Java workflows by reusing the Maven repo and the `mvnd` binary instead of downloading them every run - reduce warm-run latency for frontend/docs workflows by reusing the pnpm store - reduce overall runner consumption by canceling superseded runs and by removing one duplicated nightly backend rebuild pass This change does **not** yet split `Backend CI` into shorter feedback jobs; that is better handled as a separate pass after warm-cache numbers are available. ## Validation - parsed all workflow YAML files and the shared composite action with `python3` + `yaml.safe_load` - ran `git diff --check` ## Checklist - [x] I have read the [Contributing Guide](https://hertzbeat.apache.org/docs/community/code_style_and_quality_guide) - [ ] I have written the necessary doc or comment. - [ ] I have added the necessary unit tests and all cases have passed. ## Add or update API - [ ] I have added the necessary [e2e tests](https://github.com/apache/hertzbeat/tree/master/e2e) and all cases have passed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
