In the context that we are migrating, we are migrating build pipelines of multiple teams (each team manages multiple products, each with multiple pipelines. In that context, the choice became even easier! How we move back
, we were able to switch back without a lot of effort.įinally, changes the structure of the network made it harder to work in an efficient way with TeamCity and if there is one thing that development teams need, then it is efficiency. This combined with the adoption of cake in our environment This has now been solved with the Azure (yaml) pipelines and (yaml) templating support. , I also told that the migration to TeamCity was because of a lack of templating support in Azure DevOps.
TEAMCITY VS AZURE DEVOPS CODE
Well, it's really easy: Azure DevOps offers an integrated environment and it places your build pipelines at your fingertips, next to your code repositories (Compared to a separate build orchestrator (eg TeamCity) where you have to login into and manage your builds in a separate platform.) This integration has quite some benefits for developers, but also for the other members of the development teams can be constantly (and thus faster) up to date on the status of builds in their context. I'll explain the reasoning behind why we move back and what we use to leverage this migration. Today, I'm writing about the migration back to Azure DevOps. If you want to know more on how we did this, then I gladly refer you to this post A few weeks ago, I wrote how we migrated our build system towards TeamCity (this migration was a few years ago).
0 kommentar(er)
