gitlab-ce VS ci

Gitlab Community Edition: https://gitlab.com/rluna-gitlab/gitlab-ce for code repository version control and source code management.

I actually do .. with GitLab https://gitlab.com/rluna-gitlab/gitlab-ce

GitLab is an open-source-core collaborative development platform that has project planning and continuous integration features built in. I like it, because it is very easy to use, and yet powerful. The free hosted version gives you a lot of awesome features, but you can even self-host GitLab, as it is open-source and permissively licensed. In this series, I'm going to be showing you a few examples on how you can set it up so that you get the most out of it. Hopefully you will find it useful.

Gitea is MIT licensed, GitLab [Community Edition] is custom licensed

Besides, the Community Edition of GitLab is under an MIT license. If push comes to shove, you can get back on track by hosting your own instance without the massive harm that could come from suddenly having your project purged or otherwise losing access to GitHub. Losing issue reports or having to move to another CI platform could be a major hassle for any project.

APPVEYOR: Appveyor is an open source project builder. It works good for GITHUB repositories. The user can login to the actual VM. For more info: https://www.appveyor.com/

appveyor.com — CD service for Windows, free for Open Source

AppVeyor (GitLab/Gitea)

If you don't have an access to Mac or PC you can bundle your app for all three platforms with AppVeyor - Continuous Integration service for Windows, Linux and macOS. In short, Continuous Integration (CI) is an automated process of building, testing and deploying (Continuous Delivery - CD) application on every push to a repository.

I then do my building on a CI/CD service that offers Windows VMs free to open-source projects, with Appveyor being the first I'm aware of to start doing so.

Appveyor does as well. https://www.appveyor.com/

We were also using AppVeyor for CI during the early periods of the library and I managed to add a step at the end of the CI pipeline to do a NuGet publish, when a tag was created in GitHub. This completely removed any human error or any inadvertent omissions due to lack of time etc. This worked well for us other than the occasional NuGet publish failures due to expired API key. We had to jump into AppVeyor dashboard to see what was going on and fix things. Eventually, we migrated all the CI builds to use GitHub actions so that we can lookup things all in one-place without logging into different systems. This is a huge convenience and time saver for us. We settled on doing a manual GitHub action trigger (user invoked) especially for publishing NuGet packages rather than keep it automated so that we can inspect and keep an eye on the NuGet publish as it happens after we tag and add a release in GitHub.

I thing yes. Personally i'm use powershell scripts to deploy things via appveyor and to run something locally via task scheduler.

Can't cross-build to the MSVC or macOS targets without a license to use the Microsoft or Apple C/C++ developer tools for the final linkage against the platform libraries... and I believe even the free ones require you to have a valid license for Windows or own a Macintosh. (This can be worked around by building your release artifacts on a free-for-open-source CI/CD service like Appveyor or using the MinGW target for Windows if you don't need to link to MSVC-built libraries.)

Script source: https://github.com/appveyor/ci/blob/master/scripts/enterprise/grant_logon_as_service.ps1