rusefi

History

rusefi de5e5bab3e less fragile gradle? looks like more fragile :( only:uaefi		2025-03-02 21:24:50 -05:00
..
custom-board-build	no longer a problem with release.txt file, right?	2025-02-24 06:09:52 -06:00
hw-ci	update hardware-ci.yaml for generate config before running tests	2025-01-03 14:04:44 -05:00
build-android.yaml	making things simpler, probably without negative performance consequences	2025-01-08 14:32:12 -05:00
build-firmware-proteus-f7-mac.yaml	only:giving up on macos for now	2024-11-04 10:31:13 -05:00
build-firmware-windows.yaml	only:are they no longer installing JDK 11 by default? What has changed?	2024-12-05 12:29:18 -05:00
build-firmware.yaml	Bump ncipollo/release-action from 1.15.0 to 1.16.0	2025-02-24 08:36:14 -06:00
build-rusEFI-console.yaml	less fragile gradle? looks like more fragile :(	2025-03-02 19:29:08 -05:00
build-simulator.yaml	less fragile gradle? looks like more fragile :(	2025-03-02 19:29:08 -05:00
build-tsplugin-body.yaml	only:java version docs	2025-01-07 22:08:21 -05:00
build-unit-tests-windows.yaml	only:are they no longer installing JDK 11 by default? What has changed?	2024-12-05 12:29:18 -05:00
build-unit-tests.yaml	making things simpler, probably without negative performance consequences	2025-01-08 14:32:12 -05:00
check-pinout.yaml	Update to interactive-pinout 2.15	2024-04-19 23:48:02 -04:00
codeql-buildscript.sh	extracting ubuntu-install-tools.sh	2024-10-14 14:03:16 -04:00
codeql.yml	The Ubuntu 20.04 runner image will be fully unsupported by April 1, 2025.	2025-02-11 12:04:34 -05:00
custom-board-update-rusefi-reference.yaml	optimize branch fetching - get rid of redundant branches	2024-06-03 07:37:35 -04:00
fail_on_error.py	Add CodeQL Workflow for Code Security Analysis (#5656 )	2023-10-27 23:38:34 -04:00
gen-configs.yaml	less fragile gradle? looks like more fragile :(	2025-03-02 21:24:50 -05:00
gen-diffs.yaml	only:disable	2024-12-20 00:20:00 -05:00
gen-docs.yaml	Bump actions/checkout from 3 to 4 (#5548 )	2023-09-05 09:09:12 -04:00
gen-ibom.yaml	only:disable	2024-12-22 19:59:41 -05:00
gen-pinouts-top-level.yaml	Update to interactive-pinout 2.15	2024-04-19 23:48:02 -04:00
gen-pinouts.yaml	Update to interactive-pinout 2.15	2024-04-19 23:48:02 -04:00
hardware-ci.yaml	less fragile gradle? looks like more fragile :(	2025-03-02 19:29:08 -05:00
readme.md	Update readme.md	2024-02-24 14:13:22 -05:00
set-date.yaml	only:set-date for branches	2024-10-11 09:51:47 -04:00
sync-wiki.yaml	Bump actions/checkout from 3 to 4 (#5548 )	2023-09-05 09:09:12 -04:00

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