-
Notifications
You must be signed in to change notification settings - Fork 11
GitLab support #56
Comments
No, not really. I'm not familiar with GitLab. (I should check it out sometime 😄)
That would be awesome. We'd love to support more CI services. |
Yeah you should. It has a lot more to offer than GitHub at this point, including native CI. Okay, great. I'm working on it today for at most an hour. I'll update if I cannot file a PR by Sunday. |
Sorry, I doesn't seem to be productive to add a GitLab CI config at this moment. GitLab CI depends on running builds/tests in runners. The default cost-free runners for GitLab.com projects are Linux-based. Travis CI and AppVeyor can spin up macOS and Windows VMs as well. We need support for building for those platforms obviously. Instead of setting up VMs with the appropriate OSes I prefer to test cross-compilation first in a new purely GitLab-based project similar to this one. In this project you instead use native compilation on macOS/Windows VMs. That is to be able to test as well as build, isn't it? |
Yes. It's also much simpler to compile natively than cross compile.
I think you'll only be able to do Linux -> Windows-GNU. Crossing to Windows-MSVC or macOS requires, I think, proprietary libraries which can't be freely distributed. Still, having binary releases for Linux, perhaps even for different arches: i686, x86_64, arm, etc. via GitLab would be great progress! |
GitLab support can be had by adding a
.gitlab-ci.yml
file.Release artifacts can be produced easily, see the GitLab CI reference manual.
Is any work underway for adding this feature? If desired, I can work on this.
The text was updated successfully, but these errors were encountered: