In the previous blog post I wrote about pull request builds to help keeping the master branch clean. This time I wrote about one level higher check that can be used in Azure DevOps: pull request deploys. We deploy to a temporary site from the pull request and run some integration/UI tests against it. If it doesn't pass, merge can't be done.
Usually we have builds against the master branch. It is good but now and then builds fail and we have to fix the code. Better way would be to find errors before that. Pull request builds help with that. That way the build pipeline will be one of the "reviewer" in the pull request and doesn't pass the pull request if the build fails. In this blog post I will demontstrate how this can be done in Azure DevOps with Azure Repos.
Recently I found this Azure DevOps task by Microsoft to maintain Azure app services' appsettings. It is quite new (only 22 days old) and still in preview. In this blog post I have tried to use it and also give some hints how to manage appsettings from Azure DevOps.
Multi-tasking is an evil that reduces our effectiveness. It is true for developers but also for teams. In this blog post, I demonstrate this with the newsletter mailing simulation. It visualizes why multi-tasking takes more time than doing one task at a time. Stop starting, start finishing, and beat the evil of multi-tasking.
I wrote this how-to blog post for myself to sort out how to get code coverage for C# in Azure DevOps' build pipelines. There are many blog posts about this but this one guides how to get reports even if there are many unit test projects in Visual Studio solution.
Even if it is already the end of January I still want to summary my past year. After one year at the latest, it is nice to read for yourself how 2019 went and compare it to 2020. Keywords about what I did and learned most in 2019 are Azure, Azure DevOps, and scrum master.
This book is about the famous State of DevOps Reports; some kind of recap from years 2014-17. In this blog post I've summarized what are the impacts of continuous delivery according it. "Continuous delivery improves both delivery and performance quality."
I recently read a great book The DevOps Handbook by Gene Kim et. al. (must read for every developer!) where I first time read about heroic efforts and why they are bad things. Even if I had faced them before this was the first time I realized them and that they block automatic deploys. Start to decrease your heroic debt from today to automate you deploys.