With this post am kicking off a blog post series on working with Azure DevOps . The subjects covered by this series are organized into three categories: Azure DevOps Fundamentals Azure DevOps Advanced Azure DevOps Expert Starting with the basic of basics of Azure DevOps Fundamentals : How to create an Organization in Azure DevOps? Since it much more fun to do research and play with technology in collaboration with others, Wesley Camargo will be covering some of the topics on he’s blog , while other topics are covered by my here.
A new post and a new addition to the naming convention series . With this post I want to share my approach to naming Azure Management groups . Tip If you haven’t already, don’t forget to check out the other topics in the naming convention series : The 10 commandments for Azure naming conventions The perfect azure naming convention A naming convention to bring order to variable groups Git gud with branch naming What are Management groups and theirs limits If you are wondering about reasons for this approach to naming please have a look at the Naming convention background chapter of the The perfect azure naming convention .
In my previous post I went trough my experiences with using the basic Winget commands. And mentioned that anyone who needs more control over the installation options will quickly note that when Winget uses the default installation options when installing packages. In this post I would like to share with you how I managed to solve this and get the control I need during the installation process. Winget Advanced installation, the override command The winget install documentation shows that an --override option is available, with an input “A string that will be passed directly to the installer”.
During my summer holiday I had a one day break from sunny weather so I decided to use the family tablet to fiddle with some PowerShell. As expected only the standard software was installed on the tablet. I could either start installing everything I need manually or use this opportunity dig a bit into winget . I hope you will enjoy both the basics and the advanced configuration experience shared via this post.
With this post I want to share my approach to Git branch naming. This is the 4th and final post in the naming convention series . Tip Check out the full naming convention series : The 10 commandments for Azure naming conventions The perfect azure naming convention A naming convention to bring order to variable groups When working in large teams, managing branches can quickly become a hassle. Comparing branches to figure out their feature set, is a time consuming and error prone activity.
With this post I want to share my approach to naming Azure DevOps variable groups. This post is the 3rd in the naming convention series . Tip Check out the full naming convention series : The 10 commandments for Azure naming conventions The perfect azure naming convention Git gud with branch naming The naming convention In my experience there are a lot of different way’s Azure DevOps projects are organized. Also in contrary to the Azure resource naming variable groups are renamable and don’t possess an ability to hold additional metadata like tagging.