[ci] Automate building artifacts for master branch

plaans / aries

Toolbox for automated planning and combinatorial solving.

MIT License

39 stars 5 forks source link

[ci] Automate building artifacts for master branch #73

Closed arbimo closed 1 year ago

arbimo commented 1 year ago

This PR attempts to automated the publication as github releases of executables for the latest commit on the master branch. The executables should be published on the latest release tag: https://github.com/plaans/aries/releases/tag/latest This is a development build so should be flagged as a pre-release.

TODO:

[x] Add cross compilation for major platform (currently only linux-x86_64 is supported)
[x] Only enable the pre-release job to run once all tests have passed (currently running immediately for facilitate testing)
[x] Before merging, change the test in the pre-release job to only execute on the master (currently on deploy for testing purposes)

arbimo commented 1 year ago

The latest commit does 2 releases, each with a single binary. I suspect you should:

build the different executables on different jobs and saves them as artifacts
- have a single job that would collect all artifacts and trigger the pre-release with all binaries

franklinselva commented 1 year ago

@arbimo I have added an up-aries compilation job for the other platforms. Currently, available platforms are,

Linux amd64
Linux aarch64
Windows amd64
Windows aarch64
macOS x86_64
macOS aarch64

The Linux-aarch64 build fails with cross-compilation due to linker problems, so I have added a docker-based build for this platform. Currently, the docker-based build has consumed more time for the previous job but it was fairly quick on the up-aries repository.

franklinselva commented 1 year ago

@arbimo I have added tests for the cross-compilations.

arbimo commented 1 year ago

@franklinselva Thanks for the work on cross compilation ! I just polished this and will merge it now.