New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to specify global build directory #6276
Conversation
53a375e
to
fd88a84
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## dev #6276 +/- ##
==========================================
- Coverage 53.70% 53.56% -0.15%
==========================================
Files 50 50
Lines 9408 9438 +30
Branches 1654 1661 +7
==========================================
+ Hits 5053 5055 +2
- Misses 4056 4079 +23
- Partials 299 304 +5 ☔ View full report in Codecov by Sentry. |
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
6c64f86
to
bc0da98
Compare
Note
Reopen after rebase of #5387
What does this implement/fix?
Default implementation use
.esphome/build
folder to store build artifacts. This folder can be relatively big. I run esphome container in kubernetes and all/config
folder is mounted as remote storage. This is fine for small pregenerated json andidedata
. But this is not best option for build temporary files. Instead I can use local storage for.esphome/build
folders.This PR allows to specify
ESPHOME_BUILD_PATH
environment variable that will be used as default build folder path. This build path still can be overridden by individual components overbuild_path
option (as described in doc), but introduce default folder that can be specified.Types of changes
Related issue or feature (if applicable):
Pull request in esphome-docs with documentation (if applicable): esphome/esphome-docs#3183
Checklist:
tests/
folder).If user exposed functionality or configuration variables are added/changed: