-
Notifications
You must be signed in to change notification settings - Fork 1
Home
Moving to the next thing...
As I gain feedback about the dotnet pipelines project and I apply all that I see in the field, I see how complex the v1 solution is. In my opinion, the dotnet side of build automation (including best practice, manageability, and implementations) is in its infancy. Containers have existed for a long time in the Java world and as such have evolved into something quite good [https://github.com/spring-cloud/spring-cloud-pipelines]. But for us in the Microsoft side, containers were just introduced in the past few years. As well begin to decouple apps from the operating system and embrace a microservice style design, we are just learning about what automation looks like.
So for this next iteration of dotnet pipelines, I am going to focus specifically on VSTS deployments using a mix of managed scripts and native build steps.