-
Notifications
You must be signed in to change notification settings - Fork 112
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
Add CI workflow with artifact creation for binary flashing #540
base: master
Are you sure you want to change the base?
Conversation
Sorry, I also didn't see this one >< |
to check that the code builds on prs i suppose? and to supply prebuilt blobs for users who assembled their own unit but haven't set up a build environment locally. (it would be cool building a compilation toolchain in wasm to run in the browser in a platform-independent way.) my concern is github artifacts my age out, maybe it's worth having pushes to master push artifacts to a rolling github release (this can come later). |
Oki, still seems like a lot of maintenence work to basically upload a release every so often, dunno. |
Hi,
based on previous work I did on esp32 github projects I though it would be useful to have a CI workflow added to your gbs-control project.
Currently the sketch is compiled with all the right fqbn settings (flash layout, cpu speed, etc.), NodeMCU v1.0 as the board and esp8266 v2.7.3 as the core, but both can be easily changed.
I also added the creation of a build artifact, with the compiled sketch in bin format, two batch script files and the esptool.exe windows flashing tool to allow for (hopefully) easy binary flashing.
I have yet to test the batch scripts, they're based on the scripts I made for my most recent esp32 project (in theory they should work fine, one uploads just the sketch and the other erases wifi settings in addition to that).
Let me know what you think