search

aeonix / aeon

AEON source code (post May 2018 rebase)
Other
58 stars 43 forks source link

Build M1 binaries using Codemagic #277

Open stoffu opened 1 year ago

stoffu commented 1 year ago

M1 binaries built using Codemagic can be downloaded from

The build log is not publicly accessible, so I made a copy here

iamsmooth commented 1 year ago

Is the failed CI okay. The windows ibdtest looks like maybe it took too long but the ubuntu unit tests just failed?

iamsmooth commented 1 year ago

Also, I guess the M1 binaries won't be automatically uploaded like the others. Is the idea to just manually add that binary to a release?

stoffu commented 1 year ago

For the unit tests, this PR #278 removes the faulty test which I believe to be wrong/moot.

For the release uploads, the official account @aeonix needs to create an account at https://codemagic.io/, and follow steps described in https://docs.codemagic.io/yaml-publishing/github-releases/ for generating a GitHub access token.

I found that the token has to be of type "classic" rather than "fine-grained" and should grant access to all items under the "repo" category.

Note that the environment variable name has to be GH_TOKEN instead of GITHUB_TOKEN. Also, its group name has to be github.

I confirmed that this release upload mechanism works (see https://github.com/stoffu/monero/releases/tag/cm-test-2), but I couldn't figure out how to automatically trigger builds on Codemagic when a release tag is created. The above test was done by manually triggering the build.

I figured out that automatic build triggering is possible via webhooks, by following instructions here https://docs.codemagic.io/yaml-running-builds/webhooks/

I finally managed to trigger the build with tag creation and have the artifact uploaded, see result here https://github.com/stoffu/monero/releases/tag/cm-test-7.