I guess you pretty much expected this type of answer but there's no CI software you should use
However, here's my opinion:
I personally prefer Jenkins. It simply works and has established in the professional environment. TeamCity has a nice UI and integrates very well with other Jetbrains products. However, I prefer open source software that is well documented and supported by it's community.
As usually, it depends. If you are already using other JetBrains products, TeamCity may be a good choice. If you use GitLab, it have a good CI/CD that integrates well with their system and Travis works well with GitHub. If you are looking for something more universal that isn't closely tied to any other product, and something customizable and self-hosted, Jenkins is a good choice.
I've personally never used either, only used GitLab CI so far (which is pretty bad when self-hosting) if I were to make a choice between these two I'd say TeamCity, but Jenkins is free (I think?) and TeamCity is only free for like 5 members or something like that.
Status
This thread has been locked.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.