Re:How a Jenkins Job Broke our Jenkins UI
by maccard on Thursday June 03, 2021 @03:02PM
(#27385872)
We run everything through TeamCity. Not going to claim its the best tool in the world but it's certainly the best I've used, and it's fairly straightforward to work with!
[ Parent
| on HN ]
Re:How a Jenkins Job Broke our Jenkins UI
by regnerba on Thursday June 03, 2021 @03:15PM
(#27386027)
We use TeamCity here as well. Pretty limited in the options we have since we have most of our stuff in Perforce.
I definitely prefer TC over Jenkins though. The Jetbrains support for TC is also really good and they have been helpful whenever we contacted them or opened an issue on their public tracker.
TeamCity works well but can be a bit expensive.
It has a Kotlin DSL that is quite powerful and flexible, but of course you need to know your way around Java to make the most of it.
Custom plugins is also an option if you need something special that is not provided out of the box.
Even though I have moved on to Azure DevOps Services, it's still good to see that JetBrains have fixed a 10 year old feature request.
Re:How a Jenkins Job Broke our Jenkins UI
by throayobviousl on Thursday June 03, 2021 @06:53PM
(#27388483)
I would rather use Jenkins for all of eternity than use TeamCity again. TeamCity is probably the worst CI/CD product out there.
Can you give some examples?
Re:How a Jenkins Job Broke our Jenkins UI
by throayobviousl on Saturday June 05, 2021 @10:10PM
(#27410119)
Its been a while, but basically horrendous UI/UX, unintuitive way to create jobs and manage variables, things like that. I don't know if it was completely rewritten in the last 2 years but it was dogshit awful before 2019.