[WIP] Speed up CI tests by using the cached images for QFieldCloud

[gounux]

No description provided.

[duke-nyuki]

Task linked: QF-4996 Speed up CI tests by using the cached images for QFieldCloud

[gounux]

Here is a summary of what has been done so far, regarding speeding up the tests CI.

3 different approaches have been tried :

• using the docker/build-push-action, same as in the build_and_push release workflow

  • see this commit : the action is used 4 times, for docker-app (targets webserver_test and worker_wrapper_runtime), docker-qgis and docker-nginx
  • ❌ tests do not pass, workers seems not to be activated (see this workflow's log)
  • tried to add some network/host options, does not seem to change anything
  • cache seems to be used (see this action's summary), but loading the built image into local repository with the load: true key, which is necessary, makes build time slower

• using the docker/bake-action, which allows to build a full compose stack

  • see this commit and this commit, the bake-action is used only once, with set keys for using ghcr registry cache
  • ✅ tests do pass but are slow, ~25 minutes (~5 minutes for build + ~45 seconds for starting containers, which is not much faster than what is currently implemented)
  • registry cache seems not to be used as requested (see this action's summary)
  • the docker compose up -d job seems to rebuild some local images

• overriding the docker compose stack with a docker-compose.override.ci.yml file, which only replaces the image keys with the one previously built

  • see this commit
  • ❌ tests do not pass, targeted image suffixed with commit's SHA are not available from the ghcr repository actually
  • compose's image key does not take precedence on build key
  • this approach would force us to consider adding some changes and reviewing the way the whole docker-compose.override.*.yml files are organized and orchestrated