-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Gitlab CI #12
Add Gitlab CI #12
Conversation
Curious why you chose GitLab? I mostly use CircleCI these days and found it a big improvement on Travis but I've not tried GitLab/Azure Pipelines and some of the other new players. |
Good point, the thing is I'm in discussion with my institute admins because travis/cicle ci/codacy require additional permissions, but I wanted to setup CI as soon as possible anyway.
That was something I've seen and wanted to ask you, what is best? and why CircleCI? |
@AdamGleave I will merge it as it is needed for any further PR, but we can continue the discussion here ;) |
OK, makes sense -- thanks for setting up CI.
I like CircleCI since it easily supports parallelizing across nodes (up to 4 nodes free), and -- if you pay -- you can run on machines with more resources. This is very useful for large and slow test suites, such as if you're actually training mini-ML models as part of the suite. It seems much more actively developed than Travis and has a better UI and generally more features. Pipelines looks pretty nice and I've seen a few open-source projects migrate to this but I don't have any hands-on experience with it. |
Pipeline are nice but build for external PR are not automatic :/ (I need to create an internal branch that corresponds to each PR) |
Description
Add continuous integration using Gitlab-CI.
Motivation and Context
Addresses part of #1 .