How about CI? about hazel

[TheCherno]

My ultimate plan was to use GitLab for all of our CI needs (@Gaztin you should know about this). When I get back to Melbourne I'll take a proper look at all this and make sure we have what we need setup, including the appropriate branches.

[Gaztin]

You're right. I did know. I was simply living up to my reputation of having the worst memory. Thanks for clearing it up. I'll remove the AppVeyor as soon as the GitLab one is in place. At least we now have something that shows us if a merged PR is invalid!

[masterneko]

GitHub actions provides good CI tools. It can compile C++ for windows, Linux and mac. Why not use that?

It is basically gives you full access to a server using the command line. The only down side is that if you are using a windows server, you will have no built in package manager as many things must be done in the GUI. You can use chocolatley(windows package manager) to install the needed software to compile Hazel

[LovelySanta]

Since then github actions are introduced, and they do also support CI. I'm not sure how viable this is, but just throwing this on the table, since it wasn't an option before.

[Gaztin]

I've used AppVeyor in other projects and it is very fast and intuitive. And most importantly it won't take long to set up. Thank you for bringing it up! I'll try to get it up and running soon.

[Gaztin]

I've added AppVeyor, Future pull requests should have to pass the compilation from now on!

[Gaztin]

Looks like it's not adding checks for PRs. I think @TheCherno has to make some changes in the settings, but not sure what's blocking it. Everything looks good in the AppVeyor project.

[LovelySanta]

I just made PR #79 and it did not add any checks to it.

However shields.io is saying: , but that's on Gaztin's appveyor account.

Cherno might have to add appveyor for it to show up on the actual PR's itself.
As of now, github still does not show any checks.

[LovelySanta]

If you look in the commits; it did check cherno adding new content (not through PR)

The commit before was canceled due to 2 commits close to each other

[L4ZZA]

My ultimate plan was to use GitLab for all of our CI needs (@Gaztin you should know about this). When I get back to Melbourne I'll take a proper look at all this and make sure we have what we need setup, including the appropriate branches.

Does that mean that we will all have to port the repo from github to gitlab? How does GitLab CI handle Windows build I can't find any straight forward way to run a pipeline on GitLab CI like we do on AppVeyor were windows and VS support come out of the box.

[Gaztin]

Best case, you can self-host the GitLab runner on a dedicated server computer. That way you have total control over the environment and build tools. But that said, I don't see why you wouldn't be able to run MSBuild through the public GitLab CI?

[L4ZZA]

All I'm saying is that in order to run on GitLab CI/CD a copy of the repository is required, it will be mirrored so technically there's no need to maintain it, but I believe there are better options.

I do quite like the way GitLab CI is set up, but is not straight forward to create a windows/visual-studio build like it is on AppVeyor.
What I don't like about AppVeyor tho, is the documentation and the small, not very active community behind it.