I don’t know why but it seems like some weeks are just busier than others for everybody. And y’all have obviously been busy, because this week I got so many notifications about Agile, DevOps, GitHub and Azure DevOps articles in my inbox that it was hard to keep up. (But don’t worry, the ones that I didn’t have a chance to read this week are still queued up for me to read next week!)<\/p>\n
How I alert(1) in Azure DevOps<\/a><\/strong> Meet Utopia: DevOps with all the bells and whistles<\/a><\/strong> Continuous Delivery with SharePoint Framework and Azure DevOps to Office 365<\/a><\/strong> ASP.NET Core code coverage reports on Azure DevOps<\/a><\/strong>
\nA few months ago we announced our bounty program for security issues<\/a> in Azure DevOps. One researcher jumped on that opportunity to dig in, and wrote up the details of how they found a cross-site scripting bug in our markdown editor. Fascinating stuff!<\/p>\n
\nWhat would your perfect DevOps project look like if you could build it from scratch? Mine would start with a git repository and add some great CI build features like integrations with SonarCloud and WhiteSource. And then it would deploy using ARM templates. That’s just what Wouter de Kort has created with Utopia, a demo DevOps project with all the bells and whistles.<\/p>\n
\nLast year, I featured an article about doing DevOps for SharePoint projects, and I’m thrilled to see another. Absolutely every software project benefits from DevOps, regardless of platform, size or ecosystem. Vincent Rothlaender explains how he created a pipeline for his SharePoint Foundation application into Office 365.<\/p>\n
\nI love the flexibility in Azure Pipelines to support all sorts of custom tooling and integrations within your releases. For example, if you’re running code coverage reports on your local box, why not automate it? Gunnar Peipman shows how to generate code coverage data and add a report tab right to the build results page in Azure Pipelines.<\/p>\n