What do you like best?
Speed, speed, speed. We reduced our build time from 40 minutes to around 10 minutes. Core i7 and huge amount of RAM definitely makes lot lot of different.
We used CircleCI for a while till the day their server kept running out of memory. Common, it's not to test (and then build) bunch of Java apps on 2 (2.4 Ghz) cores and 4GB RAM. 3.8Ghz with 4 ~ 8GB of ram solve everything
Java, no problem, webpack, done at ease. All of that our quality of development completely.
What do you dislike?
Not really dislike but they definitely they can do better with test result / artifact management. Luckily, we rely on Docker for most of things, but it's definitely much nicer if Semaphore can facilitate as well. Others may find struggling when firstly adopting solution
Recommendations to others considering the product
Semaphore doesn't offer much out-of-the-box functionality, you'll may need to apply work-around here and there. But just having powerful rig is already worth a try for you
What business problems are you solving with the product? What benefits have you realized?
We work in quite strict environment that takes long time and effort to actually release. To mitigate that, we try to make sure every release is a GO, less regression, less likely to fail a microservice/integrations. That means, we have A LOT OF tests, all of them are heavy duties. Say, integration tests between all microservices, E2E test to most functionalities.
It's used to be 40 mins on CircleCI, and with just 10 minutes now on Semaphore. That's 3 times better development flow