Improved messaging if build request fails

[blckmn]

To test, you can introduce an invalid char into the custom defines.

e.g. TEST$ERROR in custom defines.

[sonarcloud]

Quality Gate failed

Failed conditions

3.5% Duplication on New Code (required ≤ 3%)

See analysis details on SonarCloud

[github-actions]

Do you want to test this code? Here you have an automated build:
Betaflight-Configurator-Android
Betaflight-Configurator-Linux
Betaflight-Configurator-macOS
Betaflight-Configurator-Windows
WARNING: It may be unstable and result in corrupted configurations or data loss. Use only for testing!

[haslinghuis]

See lot of redefines in failed builds (mostly users adding drivers already in config)

[blckmn]

AUTOMERGE: (FAIL)

• github identifies PR as mergeable -> FAIL
• assigned to a milestone -> PASS
• cooling off period lapsed -> FAIL
• commit count less or equal to three -> PASS
• Don't merge label NOT found -> PASS
• at least one RN: label found -> PASS
• Tested label found -> FAIL
• assigned to an approver -> PASS
• approver count at least three -> FAIL

[nerdCopter]

[haslinghuis]

Think we should add a link for the log

[nerdCopter]

i see, i missed the $. so this only reports failed builds, does not necessarily catch bad defines.

[blckmn]

log

There is no log at this point. It's the case where the build request itself is rejected, eg custom define formatting (invalid chars etc).