fome-fw/.github/workflows
Matthew Kennedy 1452a1dcc7 Revert "simulator: more arguments (#432)"
This reverts commit be7a2ddc9c.
2024-08-05 13:40:04 -07:00
..
hw-ci
add-ubuntu-latest-apt-mirrors.sh
build-FOME-console.yaml let's see what happens with upload-artifact@v4 2024-03-15 02:08:22 -07:00
build-firmware.yaml CI can protect us from loss of precision (#424) 2024-05-11 15:59:07 -07:00
build-simulator.yaml Revert "simulator: more arguments (#432)" 2024-08-05 13:40:04 -07:00
build-unit-tests.yaml does it fail with ASAN disabled? 2024-03-17 03:13:28 -07:00
delete-all-artifacts.yaml
gen-configs.yaml
gen-docs.yaml.disable
gen-pinouts.yaml.disable
hardware-ci.yaml
openocd_ci_f4_discovery.cfg
openocd_ci_f4_discovery_2.cfg
openocd_ci_proteus.cfg
readme.md
set-date.yaml
sync-wiki.yaml.disable

readme.md

Here is a diagram of which configure scripts are used for which workflows. This is not a complete diagram of all workflows, nor does it show everything that these jobs do.

For up-to-date information check the GitHib workflow actions (GHA) definition files *.yaml

The workflows are triggered by events: push & pull_request

flowchart TD
    gha_firmware["Firmware"]
    firmware_build[["build-firmware.yaml"]]
    gha_Console["Console"]
    Console_build[["build-FOME-console.yaml"]]
    gha_Simulator["Simulator"]
    Simulator_build[["build-simulator.yaml"]]
    gha_generate_ECU_configs["Generate configs for all supported ECUs"]
    generate_ECU_configs[["gen-configs.yaml"]]
    gha_UnitTests["Unit tests"]
    UnitTests_build[["build-unit-tests.yaml"]]
    gha_Hardware_CI["Hardware Continous Integration"]
    Hardware_CI[["hardware-ci.yaml"]]
   

    gha_firmware --> firmware_build
    gha_generate_ECU_configs ---> generate_ECU_configs
    gha_Console ---> Console_build
    gha_Simulator ---> Simulator_build
    gha_UnitTests ---> UnitTests_build
    gha_Hardware_CI ---> Hardware_CI