3 ms·

Hmm my experiences with TeamCity have been very good.

denalii 5y ago
Used it at a former job along with YouTrack and UpSource. It was super nice having everything natively integrating with each other. Of course then you deal with the relatively high JB prices for everything (not including IDEs even) and vendor lock.
axegon_ 5y ago
I'll take anything over teamcity. Even jenkins. I don't think I can go any lower than that in this universe.
- native_samples 5y ago
  What is it you dislike so much?
  - axegon_ 5y ago
    CI/CD's must be stupid simple to work with and that's their entire purpose: you should not waste time with clicking and scrolling and dealing with custom setups. Even Jenkins, which is dog shit and I've had to use in the past was light years ahead. Have a look at gitlab, github, circleci and all the big players in the field - the exact same task takes considerably less time, documentation is perfect, whatever you want to achieve is no more than 5 lines of YAML away, the UI isn't something from a 2 year old's sketchbook, the outputs are actually clever enough to work out when and where a test for instance failed and take you directly to the relevant section of the log rather than having to click "show more" and scroll up 20 times. The email notifications it sends are practically useless - they are basically images of the static noise coming from the big bang, except they clutter your inbox. And to think the company was paying close to 3000€ per year for this crap genuinely baffles me when you have an endless amount of free and open source alternatives that actually work.
    - native_samples 5y ago
      It sounds like you're talking about quite old versions, and in particular, demand something cloud hosted (not dealing with "custom setups"?). You can script it with Kotlin these days, there is a hosted cloud version, they've redesigned the entire UI (though the old version did not look like a two year old's sketchbook), it understands test output just fine and can zap you to the right place in the log (and that's always worked for me, maybe it doesn't understand your test framework output or something). But eh, different strokes for different folks. I hate YAML and much prefer having a GUI to help me set things up.

Used it at a former job along with YouTrack and UpSource. It was super nice having everything natively integrating with each other. Of course then you deal with the relatively high JB prices for everything (not including IDEs even) and vendor lock.

axegon_ 5y ago

I'll take anything over teamcity. Even jenkins. I don't think I can go any lower than that in this universe.

native_samples 5y ago
What is it you dislike so much?
- axegon_ 5y ago
  CI/CD's must be stupid simple to work with and that's their entire purpose: you should not waste time with clicking and scrolling and dealing with custom setups. Even Jenkins, which is dog shit and I've had to use in the past was light years ahead. Have a look at gitlab, github, circleci and all the big players in the field - the exact same task takes considerably less time, documentation is perfect, whatever you want to achieve is no more than 5 lines of YAML away, the UI isn't something from a 2 year old's sketchbook, the outputs are actually clever enough to work out when and where a test for instance failed and take you directly to the relevant section of the log rather than having to click "show more" and scroll up 20 times. The email notifications it sends are practically useless - they are basically images of the static noise coming from the big bang, except they clutter your inbox. And to think the company was paying close to 3000€ per year for this crap genuinely baffles me when you have an endless amount of free and open source alternatives that actually work.
  - native_samples 5y ago
    It sounds like you're talking about quite old versions, and in particular, demand something cloud hosted (not dealing with "custom setups"?). You can script it with Kotlin these days, there is a hosted cloud version, they've redesigned the entire UI (though the old version did not look like a two year old's sketchbook), it understands test output just fine and can zap you to the right place in the log (and that's always worked for me, maybe it doesn't understand your test framework output or something). But eh, different strokes for different folks. I hate YAML and much prefer having a GUI to help me set things up.