• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

Logflare / logflare / 6737100cd2a70ab7cfbd4f980b57a13fefe055e8-PR-3158
74%
main: 71%

Build:
Build:
LAST BUILD BRANCH: fix-count-query
DEFAULT BRANCH: main
Ran 12 Feb 2026 05:57PM UTC
Jobs 1
Files 455
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

12 Feb 2026 05:40PM UTC coverage: 73.559%. First build
6737100cd2a70ab7cfbd4f980b57a13fefe055e8-PR-3158

Pull #3158

github

nelsonmestevao
chore: optimize pipeline by caching docker image layers

I have considered using this
[action](https://github.com/marketplace/actions/docker-layer-caching), I
discarded it because it is not from the offical docker team.

This
[guide](https://www.blacksmith.sh/blog/cache-is-king-a-guide-for-docker-layer-caching-in-github-actions)
gives a good overview on how to accomplish this and explains why caching
images from the docker registry is in practice worst than just pulling.

I am essentially following this
[approach](https://cicube.io/blog/optimize-docker-builds-github-actions-cache/).
Pull Request #3158: chore: optimize pipeline by caching docker image layers

9887 of 13441 relevant lines covered (73.56%)

5961.37 hits per line

Jobs
ID Job ID Ran Files Coverage
1 6737100cd2a70ab7cfbd4f980b57a13fefe055e8-PR-3158.1 12 Feb 2026 05:57PM UTC 455
73.56
GitHub Action Run
Source Files on build 6737100cd2a70ab7cfbd4f980b57a13fefe055e8-PR-3158
  • Tree
  • List 455
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Pull Request #3158
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc