Go to file
rusefillc 1a5ac37ef2
Merge pull request #2 from FDSoftware/fix/docker_image
use public rusefi image on step 02, not the personal one
2024-11-03 19:09:55 -05:00
.github/workflows WIP: new runner creation scripts, fix dockerfile, added workflow for container creation 2024-10-31 01:41:49 -03:00
scripts use public rusefi image on step 02, not the personal one 2024-11-03 21:06:21 -03:00
Dockerfile add gdb-multiarch to docker image 2024-10-31 15:01:40 -03:00
README.md missing Gethla link 2024-10-31 16:50:22 -03:00
configure_ci.sh update scripts 2024-10-31 02:43:20 -03:00
old_README.md update readme, stop container before removing on update phase 2024-10-31 16:09:32 -03:00
start.sh WIP: new runner creation scripts, fix dockerfile, added workflow for container creation 2024-10-31 01:41:49 -03:00
supervisord.conf trying to add rootless docker 2023-02-06 21:23:14 -06:00

README.md

rusefi-ci

As of October 2024 it's still https://github.com/rusefi/rusefi/wiki/Dev-Quality-Control#hardware-continuous-integration

Current status: WIP

This repository is used to create self-hosted GitHub runners, from a base image, created by a workflow in the same repository, to resolve the issue: https://github.com/rusefi/rusefi/issues/7012

Host requirements for the runners host:

  • Ubuntu LTS
  • any STLink or rusEFI board connected to the host will be redirected to the docker

To start, run the start.sh script that is responsible for installing all the dependencies for the runner. After the initial setup, you can re-create or add new runners with the same script. Some steps, such as the selection of STLink/rusEFI board, were removed from the CI and moved to the creation of the runner as they are more static tasks.

For details on how to obtain STLink IDs refer to: Gethla can automatically find your device and give you the fully escaped serial.