meilisearch/MeiliSearch

Improve Docker CI speed with cache

Open

#3,782 opened on May 25, 2023

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)Rust (2,542 forks)batch import
contribution acceptedgithub actionshelp wantedmaintenanceOLD

Repository metrics

Stars
 (57,572 stars)
PR merge metrics
 (Avg merge 11d 20h) (41 merged PRs in 30d)

Description

Currently, our Docker CI is really long to compute: around 1h30

A contributor implemented Docker cache on this PR to improve the speed. However, it did not work.

As I described here, if I run the CI twice on the same commit, the cache is taken into account. But if I run the CI on two different commits (1 line of code changed) the CI lasts 1h30 again, no cache used at all.

The contributor suggested some improvements we should do here, but the team is not a Docker expert and cannot prioritize it at the moment.

So any help or contributions are welcomed! ❤️

Also, if you have any other ideas to improve the speed of the CI that is not a cache solution, you are also more than welcome to open a PR 😁

Contributor guide

Research direction
Examine the failed cache attempt in PR #3566 and the maintainer's comment about cache not persisting across different commits. Investigate Docker layer caching strategies and GitHub Actions cache actions. Consider using BuildKit's cache mounts or docker/build push action with proper cache to and cache from options.
Tech stack
dockergithub actions
Domain
ci cd
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
DockerGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65