Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci(build): add support for board-only builds #464

Merged
merged 1 commit into from
Dec 7, 2020

Conversation

innovaker
Copy link
Contributor

Lays the groundwork for CI building boards that don't require shields.

Tested using dz60rgb_rev1 board. See https://github.com/innovaker/zmk/actions/runs/397136358 for results.

Lays the groundwork for CI building boards that don't require shields.

PR: zmkfirmware#464
@innovaker innovaker force-pushed the ci-build-optional-shields branch 2 times, most recently from a8d1a41 to 9e00a67 Compare December 4, 2020 10:23
innovaker added a commit to innovaker/zmk that referenced this pull request Dec 4, 2020
Lays the groundwork for CI building boards that don't require shields.

PR: zmkfirmware#464
@innovaker innovaker force-pushed the ci-build-optional-shields branch from 9e00a67 to c2da73b Compare December 4, 2020 10:26
Copy link
Contributor

@petejohanson petejohanson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one question.

if [ -n "${{ matrix.shield }}" ]; then
SHIELD="-DSHIELD=${{ matrix.shield }}"
fi
echo ::set-output name=shield::${SHIELD}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thoughts on using something more generic, to allow other build steps to optionally add other defines?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, that's a good question and that's actually what I did for zmk-docker's workflow (which is more refined).

I suspect in this case I was just powering through and didn't take a step back before pushing.

I can see the merits so I'll refactor it and re-push.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That seems to have done the trick. This build (a PR which will build off this one) demonstrates the result:
https://github.com/zmkfirmware/zmk/runs/1501689317

innovaker added a commit to innovaker/zmk that referenced this pull request Dec 4, 2020
Lays the groundwork for CI building boards that don't require shields.

PR: zmkfirmware#464
@innovaker innovaker force-pushed the ci-build-optional-shields branch 2 times, most recently from f3746a9 to 5aafeee Compare December 4, 2020 23:03
Copy link
Contributor

@petejohanson petejohanson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, dig it!

@petejohanson petejohanson merged commit 8ad4f41 into zmkfirmware:main Dec 7, 2020
@innovaker innovaker deleted the ci-build-optional-shields branch December 7, 2020 10:44
MangoIV pushed a commit to MangoIV/zmk that referenced this pull request Dec 18, 2020
Lays the groundwork for CI building boards that don't require shields.

PR: zmkfirmware#464
tyalie pushed a commit to tyalie/zmk that referenced this pull request Nov 15, 2022
Lays the groundwork for CI building boards that don't require shields.

PR: zmkfirmware#464
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants