micrometer-metrics/micrometer

Cache baseline JARs on CI

Open

#7,102 创建于 2026年1月21日

在 GitHub 查看
 (4 评论) (0 反应) (0 负责人)Java (4,220 star) (935 fork)batch import
buildhelp wantedtype: task

描述

https://app.circleci.com/pipelines/github/micrometer-metrics/micrometer/11311/workflows/78f87759-0807-45d7-8045-9a66d945481e/jobs/62275

We had a CI build failure:

Execution failed for task ':micrometer-registry-statsd:downloadBaseline'.
> A failure occurred while executing de.undercouch.gradle.tasks.download.internal.DefaultWorkerExecutorHelper$DefaultWorkAction
   > de.undercouch.gradle.tasks.download.org.apache.hc.core5.http.NoHttpResponseException: The target server failed to respond

I've never seen this before so it's not been a significant issue, but each branch will always download the same baseline versions, which makes it a good candidate to include in the CI cache, so it doesn't repeatedly download the same JARs every CI build.

贡献者指南

技术栈
java
领域
build systemci cd
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
2
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
GradleCircleCI
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
70
研究方向
Examine the CircleCI configuration (likely .circleci/config.yml) to locate where the `downloadBaseline` Gradle task is invoked and which JARs are downloaded. Implement caching similar to existing cache steps (e.g., for Gradle dependencies) using a cache key based on the checksum of the baseline version file. Refer to CircleCI documentation on save/restore cache. Test by running a CI build to ensure cache is populated and reused.