[PR #1777] [MERGED] Enhance cache strategy with board-specific cache keys #1830

New issue

Closed

opened 2026-02-28 02:13:08 +03:00 by kerem · 0 comments

kerem commented

2026-02-28 02:13:08 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/tzapu/WiFiManager/pull/1777
Author: @anilrajrimal1
Created: 11/8/2024
Status: ✅ Merged
Merged: 12/11/2024
Merged by: @tablatronix

Base: master ← Head: feat/cache-keys-per-board

📝 Commits (2)

ad651ae fix(compile_example.yaml): Fix cache key inconsistency and correct typo in 'Compile examples' workflow
5874ab5 feat(compile_library.yml): Use board-specific cache keys to avoid conflicts

📊 Changes

2 files changed (+29 additions, -11 deletions)

View changed files

📝 .github/workflows/compile_examples.yaml (+21 -8)
📝 .github/workflows/compile_library.yml (+8 -3)

📄 Description

Summary:

This PR refines the caching strategy used in the Compile Library GitHub Actions workflow by making cache keys board-specific. Previously, caches for pip and PlatformIO were shared across all board configurations, which could lead to cache conflicts or inefficiencies. Now, each board (e.g., nodemcuv2, lolin32) has its own unique cache, improving cache hits and reducing build times.

Changes:

Modified cache keys for pip and PlatformIO to incorporate the board matrix value.
This change ensures better cache management when multiple boards are being built, preventing cache collisions.

Motivation:

This change improves the efficiency of the CI/CD pipeline by ensuring that the cache is appropriately scoped for each board, optimizing build times for different configurations.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/tzapu/WiFiManager/pull/1777 **Author:** [@anilrajrimal1](https://github.com/anilrajrimal1) **Created:** 11/8/2024 **Status:** ✅ Merged **Merged:** 12/11/2024 **Merged by:** [@tablatronix](https://github.com/tablatronix) **Base:** `master` ← **Head:** `feat/cache-keys-per-board` --- ### 📝 Commits (2) - [`ad651ae`](https://github.com/tzapu/WiFiManager/commit/ad651aec7c1b895a9a447d30b54aa90f72ff34a3) fix(compile_example.yaml): Fix cache key inconsistency and correct typo in 'Compile examples' workflow - [`5874ab5`](https://github.com/tzapu/WiFiManager/commit/5874ab512cbb9fd8b2fd2b3f91dfc3b1a256df3f) feat(compile_library.yml): Use board-specific cache keys to avoid conflicts ### 📊 Changes **2 files changed** (+29 additions, -11 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/compile_examples.yaml` (+21 -8) 📝 `.github/workflows/compile_library.yml` (+8 -3) </details> ### 📄 Description ### Summary: This PR refines the caching strategy used in the `Compile Library` GitHub Actions workflow by making cache keys board-specific. Previously, caches for `pip` and `PlatformIO` were shared across all board configurations, which could lead to cache conflicts or inefficiencies. Now, each board (e.g., `nodemcuv2`, `lolin32`) has its own unique cache, improving cache hits and reducing build times. ### Changes: - Modified cache keys for `pip` and `PlatformIO` to incorporate the board matrix value. - This change ensures better cache management when multiple boards are being built, preventing cache collisions. ### Motivation: This change improves the efficiency of the CI/CD pipeline by ensuring that the cache is appropriately scoped for each board, optimizing build times for different configurations. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>