3 ms·
I had the misfortune of having to use GitLab CI recently. GitLab gets a lot of leeway from HN, maybe because it's an underdog, but it wasn't ready for prime tim
by vraivroo 7y ago
I had the misfortune of having to use GitLab CI recently. GitLab gets a lot of leeway from HN, maybe because it's an underdog, but it wasn't ready for prime time. Several features were just broken, and several more did things in surprising ways (not what you usually want to see in a key infrastructure component).
- chatmasta 7y agoDefinitely, it has its problems. The documentation also seems to lag behind the product (and there are duplicated pages for CE and EE, very confusing). Personally it was easy for me to switch from travis because all my CI scripts are actually bash scripts, so the .yml CI file is just a few lines pointing to those scripts. All I had to do with gitlab was make a base image to be the "CI image" with all the tooling necessary + docker-in-docker.