custom-board-bundle-sample-.../firmware/config/boards
GitHub build-firmware Action 8188ab7d90 Auto-generated configs and docs 2020-09-09 06:44:30 +00:00
..
frankenso progress 2020-08-17 19:51:50 -04:00
hellen/cypress Hellen says Cypress 2020-09-07 11:32:02 -04:00
kinetis Auto-generated configs and docs 2020-09-09 06:44:30 +00:00
me7_pnp reorder ADC channel index (#1763) 2020-09-06 18:25:26 -04:00
microrusefi microRusEFI used as Body Control Module BCM BCU 2020-09-07 16:25:00 -04:00
nucleo_f746
nucleo_f767
nucleo_h743
prometheus Merge remote-tracking branch 'origin/Hellen_fork_point' into master 2020-09-07 15:32:15 -04:00
proteus Multiple knock sensors (#1745) 2020-09-02 07:19:02 -04:00
skeleton Merge remote-tracking branch 'origin/Hellen_fork_point' into master 2020-09-07 15:32:15 -04:00
st_stm32f4
STM32F407VET6_Black.bat
STM32F407VET6_Mini.bat
clean_env_variables.bat
clean_env_variables.sh price of lazy progress 2020-08-31 20:56:46 -04:00
common_make.bat
common_make.sh
readme.md

readme.md

See misc/jenkins/compile_other_versions/run.bat which is executed by build server.

See https://rusefi.com/build_server/

By definition, BOARD_NAME is a folder in firmware\config\boards

One BOARD_NAME could be producing a number of artifacts via compile_$BUNDLE_NAME.sh scripts

Work in progress: SHORT_BOARDNAME becomes BUNDLE_NAME