Course Introduction
Intro to Version Control and Git
Branching
Permissions
Non-Azure Repos and Pipelines
Course Summary
The course is part of these learning paths
This course explores how to implement version control on Azure repos. It begins with an overview of what source control is and the different types of source control available. It then looks at the key elements of branching, different branching strategies, and how they impact the development process. You'll move on to learn about pull requests and merging as repository functions, and the different merging scenarios available to you. Finally, you'll be guided through using third-party systems in conjunction with Azure DevOps. This course contains several guided demonstrations from inside the Azure portal to give you real-world exposure to the concepts covered throughout the course.
If you have any feedback relating to this course, please feel free to reach out to us at support@cloudacademy.com with any questions or comments.
Learning Objectives
- Understand what version control and Git-based repositories are
- Learn about branching and the branching strategies
- Learn about pull requests and merging in Azure DevOps
- Set permissions on repositories and on TFVC in Azure DevOps
- Use Azure DevOps in conjunction with build pipelines set up on other platforms
Intended Audience
This is an intermediate level course suited to developers, engineers, and project managers.
Prerequisites
To get the most out of this course, you should have a basic understanding of the software development lifecycle. Knowing what's involved in deploying software to a production environment would also be helpful. If you want to follow along with the demonstrations in this course, you'll need to have an Azure DevOps account.
Let's see how the Git variant of Azure DevOps repo permissions work. As with the earlier TFVC repo, go to project settings and click repositories under repos. I'll go to the repository and allow Hallam Sql to bypass policies when pushing to the repo. We can see that permission has been propagated down to the branches. Now for some inexplicable sadistic reason, I will deny him the ability on the list server DBs, and DB select with tree view branches while leaving that permission intact for the master branch. Whatever your motivation, these permissions at repo or branch level will allow you to bypass for individuals or groups, any branch policies you have implemented.
Hallam is a software architect with over 20 years experience across a wide range of industries. He began his software career as a Delphi/Interbase disciple but changed his allegiance to Microsoft with its deep and broad ecosystem. While Hallam has designed and crafted custom software utilizing web, mobile and desktop technologies, good quality reliable data is the key to a successful solution. The challenge of quickly turning data into useful information for digestion by humans and machines has led Hallam to specialize in database design and process automation. Showing customers how leverage new technology to change and improve their business processes is one of the key drivers keeping Hallam coming back to the keyboard.