![]() ![]() ![]() I’ve figured I could run at least 3 Gitlab runners and still be able to work normally without noticing any slowdown.Īs you can probably guess, this worked fine for some time, but then the team and the app grew, and the build times grew with it. Starting more servers for 2 devs that would run 24/7 and do nothing most of the time seemed wasteful when I had an overpowered desktop that I was utilizing at barely 30%. When COGVIO started in 2017, we had an on-premise Gitlab instance and needed Gitlab runners. In modern software development, it’s unimaginable that you don’t have some CI/CD build server hooked into your version control, so I probably don’t have to introduce Gitlab CI/CD.īut how do you do that effectively, to save money and time? The story ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |