search

dstroy0 / InputHandler

Arduino input handler
https://dstroy0.github.io/InputHandler/
GNU General Public License v3.0
1 stars 0 forks source link

build binaries workflows #61

Closed dstroy0 closed 1 year ago

dstroy0 commented 1 year ago

Dependency adventures! Linux is fun!

dstroy0 commented 1 year ago

Just trying to get rid of the WARNINGS in the build logs.

dstroy0 commented 1 year ago

Then I'll worry about saving the built binary.

dstroy0 commented 1 year ago

it looks like it's building with no warnings, I'll figure out how to save it to the repo and test it tomorrow

dstroy0 commented 1 year ago

Ok now I just need to figure out how to push the changes in the CI.

dstroy0 commented 1 year ago

Ok, I cloned the main branch into release and protected release so this workflow should finish correctly now, just waiting on it now.

2bndy5 commented 1 year ago

Apparently, the set-output command is now deprecated in GitHub action workflows. They recommend using a new variable in the github env file: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#environment-files

dstroy0 commented 1 year ago

Yeah, some external actions are using set-output.

2bndy5 commented 1 year ago

yeah, we plan to migrate the cpp-linter action to the env file approach soon.

dstroy0 commented 1 year ago

It looks like this is fixed. I want to tweak the CI a bit more but this is working fine. A build happens on push to tools/cli_gen_src that targets tools/bin/latest and one on release to tools/bin/release.

2bndy5 commented 1 year ago

There is a way to upload build artifact from the CI to a published release's assets (which by default is just a zip and tar.gz files containing a snapshot of the repo at the tagged commit): see csexton/release-asset-action.

I often upload my CI build artifacts using actions/upload-artifact