|
|
|
|
|
by kickopotomus
1737 days ago
|
|
> it crashes all the time, features are so amateurish (vs teamcity especially) that we're struggling just to do basic things. Do you have an on-prem instance? What sort of features does teamcity have that are not there in Gitlab CI? Teams in my org are currently switching from Gerrit/Jenkins combos to Gitlab and I have been pretty pleased so far. I do wish there was a nicer way to experiment with different CI configurations from within the browser to prevent a bunch of pointless commits messing with your config YAML; but, otherwise I have been pretty happy with the flexibility. |
|
But why do we need so much work to write the script ? Why is the reporting so bad on test failure, why building complex dependency chains running in parallel and in sequence doesnt work ? Why do we need to touch the repo to change the build descriptor?
It's just not as fun to use, immediate, beautiful, and productive. It's thrown on top of the git part, half assed.