Pull Request Checks to Next Level with Deploys

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.

Build Already in Pull Request and Builds Won’t Fail

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.

The Evil of Multi-Tasking

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.

Heroic Efforts Block Automatic Deploys

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.