I am sure there is a resolution to get away from this issue, but I couldn’t think much about it. This takes a significant amount of time for a single build to happen. NET framework application, it is advisable to use VS 2017 Hosted agent since it will have VS 2017, Docker, Azure CLI, etc., installed as part of the configuration. Secondly, each build will trigger the rigorous process of spinning up the hosted agent, installing Framework SDK and prerequisites for a successful build. First of all, you have a limitation of 1800 minutes of build by any of the hosted agents. While in one of my post I have used Azure DevOps project to implement the same scenario, I did encountered several issues with that approach. NET framework 3.5 application and deploy it to Azure Kubernetes Cluster. Folks, I had been thinking for a while to implement a full CI/CD cycle for docker containerization of a legacy.
0 kommentar(er)
