Cache baseline JARs on CI · micrometer-metrics/micrometer#7102

(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
難度: 2
預計時間: 1-3 hours
活動狀態: fresh
清晰度: clear
前置要求: GradleCircleCI
新手友善度: 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.