build in parallel and some cleanup#156
Conversation
|
Should we take the opportunity to also set a specific IDF-version as discussed in #150 in this PR or shall we do that in a separate PR? I'm thinking that using a .env file with the IDF-version would be the best way. That'd allow for a single place to set the IDF-version from which both By updating docker.compose.yml, Dockerfile and build-docker-image.sh we could even allow easy switching between versions locally if someone wants to run against another version than what we set as default (v4.2?) |
|
from an other thread I was reading that you like building against the latest master branch. So I was not considering this solution. |
|
I do like building against the master branch, but now that Espressif (allegedly) have fixed the PSRAM issues that were only available in master, that need has lessened. And, with the sudden upsurge in users of Smooth, it makes sense to build against an official release of IDF, while still giving the option to build against master by simply changing a file and building the image locally. |
Updates for new I2C sensor SHT30 (#150)
- load IDF-version from .env file - set IDF-version in Dockerfile - use the IDF-version for the new tag - read new image name from .env file for fast switching
|
as you can see now, with the If it is okay for you I would try to implement some kind of check if there is a newer IDF image available, building the new image and uploading it to your docker hub or github packages if all tests are successful. of course i would need some kind of API key in the github actions environment. edit: it would be even possible to try/check different IDF-versions on github actions. |
|
Very nice. I'm not sure automatically updating the image is the right way to go as it introduces a moving target in he build chain. However, a step that fails if there is a new release available could be a good thing if it isn't set to be a required success in the branch protection settings. I like the idea of building against both |
- build host image local - update github actions to build different IDF-versions
|
I had an idea which I want to present to you:
I like this approach very much as it is very clean and easy to maintain. |
|
Oh, that's a really nice solution. Once Ubuntu 20.04 is available we can update the script to that. |
use Ubuntu 20.04 for the docker image
|
Ubuntu 20.04 is already available in docker :) edit: i just checked Dockerhub: there is even a 20.10 and 21.04 available. I will try the 21.04 in the end. |
PerMalmberg
left a comment
There was a problem hiding this comment.
Maybe a note in the readme explaining the build process, how to select an IDF-version locally?
Also, please update the contributors file to list this PR
|
From my side I am now happy with the current changes. |
PerMalmberg
left a comment
There was a problem hiding this comment.
Just a few typos to fix before merging.
|
Ah stupid mistakes. I fixed them all. |
|
Awesome, merged! |
I did some small tasks in this pull request: