Introducing CI using GitHub Actions about lovyangfx HOT 4 CLOSED

The implementation appears to have been a success.
Thank you very much.

from lovyangfx.

@estshorter thanks for your input 👍

Given the scope of this library, a few basic parallel jobs are required:

• ESP32 / Arduino
  • windows
  • mac
  • linux
• ESP32 / Platformio
  • windows
  • mac
  • linux
• ESP32 / esp-idf
  • windows
  • mac
  • linux
• SAMD / Arduino
  • windows
  • mac
  • linux

This is only the shallowest scope though, each job should also be tested against every combination of board selection + display device selection in order to be exhaustive.

The problem I've had when researching this is that such exhaustivity triggers billing on the github account (or exhausts whatever budget there is)

Unfortunately without this exhaustivity the tests are weak and question the utility of the CI, so maybe a self-hosted test suite is more appropriate ?

from lovyangfx.

I'm having problems with my recent release of LovyanGFX causing compile errors on SAMD51. Sorry about that.

The internal type representation is different between ESP32 and SAMD51, so we need to describe the types strictly.
Since I usually work with ESP32, I often miss compile errors in SAMD51.

from lovyangfx.

#151 added 3 separate workflows ArduinoBuild, PlatformioBuild and IDFBuild

The existing build using Arduino CI has been kept as is.

On push/pull-request, each workflow will create parallel jobs to test different boards.

from lovyangfx.