googleapis / googleapis/google-cloud-java

Make Maven Fmt/ Lint Job Run Faster

未关闭
#11,598 0 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看
priority: p3 type: feature request
主要语言
Java
星标
2.1k
派生
1.2k
平均合并
1 天 23 小时
30 天内合并 PR
157

描述

From a recent run of the lint job (https://github.com/googleapis/google-cloud-java/actions/runs/15201184035/job/42755490835) took ~30 minutes to run.

![Image](https://github.com/user-attachments/assets/ca28b10b-78dc-4e4a-8871-45465da7d4f1)

Can we make this run faster?

Job details (https://github.com/googleapis/google-cloud-java/blob/80a9d63203bc7e12a8ed2a7cd0eb06450c3ce03e/.github/workflows/ci.yaml#L82) looks to try and run this in parallel.

Additional options to explore:
- Can we only fmt this on modules that have code changes instead of running this for the entire repo?
- Can we only fmt on PRs that have code changes (exclude CI or deps upgrades)?
- Does the fmt plugin to help speed this up natively? Some configurations that we can play around with?

贡献指南

打开贡献指南

调研方向

Start with the Maven fmt/lint job in .github/workflows/ci.yaml around line 82 and review the linked run to identify where the roughly 30 minutes is spent. Compare options for limiting work to changed modules or relevant pull requests, and verify that the job remains correct while running faster.

由索引模型根据 Issue 内容生成。

评估

技术栈
github-actions, java
领域
build-system, ci-cd, performance
Issue 类型
重构
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
需要澄清
新手友好度
35/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。