4/11/2023 0 Comments Teamcity github webhook![]() There should be reference pipeline definitions that can be used easily, but teams still should be able to customize everything. We should standardize our build pipelines.After a few rounds of discussions we settled on the following list of priorities: What goals did we have?Īs migration was becoming inevitable, we decided to describe the ideal CI solution - in essence, all points we could improve if we would re-implement anyway. It was time to look for a solution that better fit our scale and ambitions. The final push arrived when Travis announced their new pricing model, increasing our cost by a factor of 4x without providing any benefit. We had 20 concurrent builds which clearly was not enough anymore. In the afternoon your build could sit for over an hour waiting to start. And that was after we fixed a few obvious bottlenecks in the old setup already. ![]() It would take around 45 minutes (45 minutes, Carl!) to build our largest repo. We had quite a few regular complaints about our CI setup before migrating: Quite impressive right? In the remainder of this post, we’ll share why we did this and how we tackled this challenge. While doing that we standardized our pipelines, reduced the build/queue time, and took control of our build agent hardware and environment. We, therefore, migrated 75 repositories from Travis CI to TeamCity in a few months’ time. Was it really supporting our teams after the enormous growth we went through? Turns out, that was not the case. That’s why we took a hard look at our Travis CI setup last year. Without a smooth build and test setup teams lose productivity and everything grinds to a halt. ![]() Continuous integration forms the backbone of every tech company. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |