DEV Community

Discussion on: whats the best CI/CD service

Collapse
 
sarafian profile image
Alex Sarafian

I've worked with many different services and I've learned that when they offer too much ui, then they become dangerous for the team. In my opinion, every project should have defined entry points for e.g. build, test, publish and all the rest are just a matter of driving them with any tool of preference. Then you also have portability from tool to tool.

I've seen a team struggling so bad with gitlabs to a point that I hated it because it offers this culture of just clicking sound that bad developers embrace. If of containing their complicated actions in the repo itself, they choose to implement complex paths outside because why should they code it? When the repo changes though, then the whole system breaks apart. If you are spending more time troubleshooting your ci, then you are doing something wrong.

Any tool should have a very clear change management process embedded in like yaml. I love Travis and appveyor because they allow the configuration and execution to be part of the branch with a very simple and readable format.