We experienced many different emotions with what seemed like a daunting task. What made it less daunting, the facilitators reminded us, was that we are not alone - we are team - so, leverage each other.
DevOps, among other things, is about collaboration, and a shared responsibility for delivering features into production. Your Definition of Done should reflect this. Learn why and how you should explicitly define Done to improve collaboration and quality.
Azure DevOps applies to any language, any platform including Arduino. In this post, I will show you how to build Arduino microcontrollers using Azure DevOps Build pipeline and a custom build agent.
Migrating from Bitbucket to Azure DevOps is a quick and easy process. Once your code is in DevOps, you’ll have access to all the powerful services Azure has to offer.
Learn how DoD leverages Azure DevOps to promote code from higher information level (IL) environment from a lower IL environment using Microsoft-Hosted and Self-Hosted Agents.
In this post, we will show you how to retrieve Azure DevOps permissions using the REST APIs with NodeJS. You can use this as a starter to consume other Azure DevOps REST APIs as documented at https://docs.microsoft.com/en-us/rest/api/azure/devops/?view=azure-devops-rest-5.0.
As part of an organization’s automated Release pipeline, it is important to include security scans and report on the results of these scans. One tool used in the industry is the OWASP Zed Attack Proxy (ZAP).
While it’s worth mentioning that hosting web applications using Azure PaaS offerings or via containers would be the preferred route for a variety of reasons, VMs are still widely used in many organizations. With that scenario in mind, this post is geared to helping you get started with streamlining your release process. As a note, much of this process translates easily to using Azure PaaS offerings.
I love to learn about new technologies. You install the product, grab a few samples, pour over blogs & documentation and away you go. I have found over the years as systems have gotten more complex its harder to explore new products. Sure you can install them, VMs have even made that quick, you don’t even have to install. But to truly explore you really need the data. Even worse, a lot of the time the samples are just a small subset of the scenario and require a lot of work to go beyond the basics. But the Azure DevOps team has put together a great program with dive in, enter Azure DevOps Hands-On Labs.
Depending on what version of TFS you intend to migrate and what features you are using, there are a few things that in my opinion are “major” considerations because they have the potential of adding scope to your migration efforts. While you will find out about them as you read through the official migration guide, I believe there is value to knowing these things prior to embarking in such journey.