rusefi

History

dependabot[bot] c90a78f44b Bump mikepenz/action-junit-report from 4 to 5 (#7036 ) Bumps [mikepenz/action-junit-report](https://github.com/mikepenz/action-junit-report) from 4 to 5. - [Release notes](https://github.com/mikepenz/action-junit-report/releases) - [Commits](https://github.com/mikepenz/action-junit-report/compare/v4...v5) --- updated-dependencies: - dependency-name: mikepenz/action-junit-report dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>		2024-11-04 06:49:37 -05:00
..
custom-board-build	only:smarter default tunes output folder	2024-10-09 01:02:05 -04:00
hw-ci	only:nucleo_f767	2024-10-31 00:03:52 -04:00
build-android.yaml	let's start using java 17 for half of the workflows	2024-09-04 22:11:22 -04:00
build-firmware-proteus-f7-mac.yaml	only:common_submodule_init.sh	2024-10-08 18:32:09 -04:00
build-firmware-windows.yaml	let's start using java 17 for half of the workflows	2024-09-04 22:11:22 -04:00
build-firmware.yaml	extracting ubuntu-install-tools.sh	2024-10-14 14:03:16 -04:00
build-rusEFI-console.yaml	Bump mikepenz/action-junit-report from 4 to 5 (#7036 )	2024-11-04 06:49:37 -05:00
build-simulator.yaml	extracting ubuntu-install-tools.sh	2024-10-14 14:03:16 -04:00
build-tsplugin-body.yaml	knock spectrogram makes TS plugin useful again	2024-11-01 11:29:12 -04:00
build-unit-tests-windows.yaml	let's start using java 17 for half of the workflows	2024-09-04 22:11:22 -04:00
build-unit-tests.yaml	extracting ubuntu-install-tools.sh	2024-10-14 14:03:16 -04: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	let's start using java 17 for half of the workflows	2024-09-04 22:11:22 -04: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	…
gen-configs.yaml	let's start using java 17 for half of the workflows	2024-09-04 22:11:22 -04:00
gen-diffs.yaml	…
gen-docs.yaml	…
gen-ibom.yaml	…
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	only:one step back	2024-10-31 22:24:26 -04:00
openocd_ci_f4_discovery.cfg	Use env vars to define serial devices	2024-03-13 09:50:09 -04:00
openocd_ci_proteus_f4.cfg	Use env vars to define serial devices	2024-03-13 09:50:09 -04:00
openocd_ci_proteus_f7.cfg	Use env vars to define serial devices	2024-03-13 09:50:09 -04:00
readme.md	…
set-date.yaml	only:set-date for branches	2024-10-11 09:51:47 -04:00
sync-wiki.yaml	…

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