Started by GitHub push by ti-chi-bot[bot]00253792537971010710101.035163351630106173978397833779e3c33ebef1dca8ddffdbc09bcb3762dd59cd8389e3c33ebef1dca8ddffdbc09bcb3762dd59cd838origin/main9e3c33ebef1dca8ddffdbc09bcb3762dd59cd8389e3c33ebef1dca8ddffdbc09bcb3762dd59cd838origin/main9e3c33ebef1dca8ddffdbc09bcb3762dd59cd8389e3c33ebef1dca8ddffdbc09bcb3762dd59cd838origin/mainhttps://github.com/PingCAP-QE/ci.githttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/377/artifactshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/377/changeshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/377/https://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/377/testsfalse#3777101080415seed #377377falsefalse377201829SUCCESS1725526400096https://do.pingcap.net/jenkins/view/all/job/seed/377/default-r65vh- pipelines/pingcap/tiflash/latest/pull_integration_test.groovypipelines/pingcap/tiflash/latest/pull_unit_test.groovy9e3c33ebef1dca8ddffdbc09bcb3762dd59cd8381725526360000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comfeat: cache build in tiflash pipeline (#3107)
For PRs with significant changes, tiflash build binary generally takes
25 minutes. For some test instabilities or environment issues causing
pipeline execution failures, repeatedly building the same commit SHA
binary of a PR is unnecessary; therefore, adding a build cache is used
for acceleration.
2024-09-05 08:52:40 +00009e3c33ebef1dca8ddffdbc09bcb3762dd59cd838feat: cache build in tiflash pipeline (#3107)editpipelines/pingcap/tiflash/latest/pull_integration_test.groovyeditpipelines/pingcap/tiflash/latest/pull_unit_test.groovy
githttps://do.pingcap.net/jenkins/user/noreplynoreplynoreply