Skip to content

Commit

Permalink
CI: use more generic version of build-results
Browse files Browse the repository at this point in the history
this way only the `needs` list needs to be adapted and the step is fully
generic. i wasn't aware of this trick when i first wrote
`build-results`.
  • Loading branch information
rursprung committed Mar 1, 2025
1 parent b3a44d8 commit ef961cc
Showing 1 changed file with 8 additions and 7 deletions.
15 changes: 8 additions & 7 deletions .github/workflows/CI.yml
Original file line number Diff line number Diff line change
Expand Up @@ -88,11 +88,12 @@ jobs:
name: Final Results
if: ${{ always() }}
runs-on: ubuntu-latest
needs: [lib, stm32f4-event-printer]
needs:
- lib
- stm32f4-event-printer
steps:
- name: check for failed builds of the library
if: ${{ needs.lib.result != 'success' }}
run: exit 1
- name: check for failed builds of the example
if: ${{ needs.stm32f4-event-printer.result != 'success' }}
run: exit 1
- name: "check for failed builds"
run: |
cat <<EOF | jq -e 'unique | all(. == "success")'
${{ toJson(needs.*.result) }}
EOF

0 comments on commit ef961cc

Please sign in to comment.