That’s interesting, as we have just completed a huge migration of our CI/CD infrastructure off Teamcity, for plenty of reasons but “we’re paying a shit ton of money for this and it’s a pain in the ass” was a major one.

They seem to be very bloated and unable to modernize their product lines.

▲

jazdw 41 minutes ago | parent | next [-]

I've been thinking about doing the same, what did you migrate to? I was thinking GitHub actions but the outage yesterday reinforced that it might be a bad idea.

	▲	stingraycharles 36 minutes ago \| parent [-]
		We migrated to buildkite, as it allowed self hosted agents and lots of “building blocks” to extend stuff ourselves. One of the things we really use heavily is dynamic pipelines, as we have a lot of different stuff. In teamcity, we had close to 1k build configs, and were able to replace this with about 20 dynamic pipelines in buildkite. We did need to do a bunch of plumbing, but in this age of AI it means our developers don’t have to rely on devops anymore to get their stuff done to make all this work. One of the problems was that our devs were “afraid” to alter teamcity build configs, as it all was more fragile than it should be and they were afraid to break stuff. Teamcity allows for customization with plugins, but all that is so bloated with either Java or Kotlin and requires a shitton of domain specific knowledge to pull off. Buildkite is much simpler with YAML and their plugin infrastructure which is effectively just hooks into scripts. It’s well designed.

▲

ActionHank 42 minutes ago | parent | prev [-]

Interesting, what did you migrate to? We've had mixed results in reliability between ADO and Github actions.