If run manually from actions when it finishes the process attaches as artifacts the build. This is useful for testing.
If you make a release it runs automatically and attaches the files to the release as a download.
The pipeline runs on the images provided by github which are for: win, mac and ubuntu. For the rest of the OS could be done with jobs using the ubuntu image that has docker installed... and taking advantage of that try to do the rest of the builds.
Other clarifications:
The branch master is no longer compiling for me, so the tests are repeated against the tag of the latest stable version.
Ubuntu is completely finished (that's why it has the added steps to process the build).
In windows it is necessary to make some adjustment of paths that from what I noticed are failing the check_file. I left a fix in this branch but I never saw the result so I don't know if the build is finished.
Mac still doesn't compile, I will try to run the steps manually on my work mac to see if I understand why.
horsicq
commented
1 month ago
The pipeline works as follows:
Other clarifications:
I leave the pr open to be working on it here. Test run (tag 3.09 + this patch): https://github.com/xchwarze/DIE-engine/actions/runs/9932527015