Summary
This course introduces Azure DevOps, covering its core concepts like Version Control, Continuous Integration, and Continuous Deployment. It details the DevOps lifecycle, the benefits of adopting DevOps culture, and the specific services offered by Azure DevOps (Boards, Repos, Pipelines, Test Plans, Artifacts). The course also contrasts Waterfall and Agile methodologies and provides practical guidance on setting up an Azure DevOps account, managing organizations and projects, and utilizing repositories and build/release pipelines, with a focus on practical implementation through labs.
Key Insights
DevOps bridges the gap between Development and Operations teams in the software lifecycle.
DevOps is a culture and practice that fills the gap between development and operations teams, similar to how Agile addressed the gap between business and development. It emphasizes collaboration throughout the entire software development lifecycle to ensure product quality and environmental consistency.
DevOps is fundamentally a culture and practice, not just tools or methodologies.
DevOps is fundamentally a culture and practice that fosters collaboration between development and operations teams to ensure product quality and reliable performance across different environments. It is not merely a tool, process, methodology, or technique.
Work item processes (Basic, Agile, Scrum, CMMI) define the types of work items and workflows available in Boards.
The choice of a work item process (like Basic, Agile, Scrum, CMMI) during project creation dictates the available work item types (e.g., Epic, Issue, Task, Bug, Feature, Product Backlog Item) and the workflow states visible in Azure Boards.
Sections
Introduction to DevOps and Azure DevOps
Overview of Azure DevOps course structure and learning objectives.
The course aims to provide a comprehensive understanding of Azure DevOps, covering Version Control, Continuous Integration, Continuous Delivery, and more, to equip learners with skills for efficient software development and deployment.
Azure DevOps course outline includes introductory topics, setup, features, and advanced concepts.
The course outline covers an introduction, project space setup, key features, Source Control with Git, Continuous Integration using TF VCS and Git, and deploying applications on a virtual machine, comprising approximately 25 labs from beginner to advanced levels.
Traditional software development lifecycle involves planning, coding, building, testing, deployment, and operations.
The traditional software development lifecycle includes distinct stages: plan, code, build, test, deploy, and monitor. In small teams, one team handles all stages, while larger organizations often have separate teams for planning (business/product owner), development (developers/testers), and operations.
DevOps bridges the gap between Development and Operations teams in the software lifecycle.
DevOps is a culture and practice that fills the gap between development and operations teams, similar to how Agile addressed the gap between business and development. It emphasizes collaboration throughout the entire software development lifecycle to ensure product quality and environmental consistency.
DevOps is fundamentally a culture and practice, not just tools or methodologies.
DevOps is fundamentally a culture and practice that fosters collaboration between development and operations teams to ensure product quality and reliable performance across different environments. It is not merely a tool, process, methodology, or technique.
Automating processes is key to DevOps, enabling lifecycle execution on each code commit.
Numerous tools exist in the market to automate DevOps processes. These tools enable the entire software development lifecycle (plan, develop, deploy) to occur automatically on each code commit, ensuring continuous quality checks and operations.
DevOps learning is beneficial for all software development team roles and for individual contributors.
DevOps is relevant for developers, testers, product owners, Scrum Masters, operations teams, individual developers, freelancers, management, and even clients, as it improves process efficiency, development speed, and provides clear insights into project progress.
Key benefits of DevOps include faster delivery, reduced time, easier rollbacks, improved quality, and enhanced collaboration.
DevOps leads to faster delivery by automating deployment, reduces overall time by automating testing and rollbacks, improves code quality through automated checks, and fosters collaboration among all teams involved in product development.
Azure DevOps is a set of modern services for planning, collaboration, and faster delivery.
Azure DevOps is a suite of modern Microsoft services designed to help teams plan smarter, collaborate better, and ship faster. It can be used by selecting specific services based on role or by utilizing all services together for comprehensive lifecycle management.
Azure DevOps, formerly VSTS, is a Microsoft-managed, secure, and reliable cloud service.
Azure DevOps was formerly known as Visual Studio Team Services (VSTS). Being developed, managed, and maintained by Microsoft, it offers a fast, secure, and reliable platform accessible via a web browser.
Azure is a broad cloud platform, and Azure DevOps is a feature or service within it.
Azure is a comprehensive cloud solution offering numerous services. Azure DevOps is a specific feature or service within Azure, focusing on the development lifecycle management.
Azure DevOps offers five core services: Boards, Repos, Pipelines, Test Plans, and Artifacts.
The five integrated services of Azure DevOps are Boards (planning and tracking work), Repos (code management with Git/TFVC), Pipelines (CI/CD automation), Test Plans (testing and quality assurance), and Artifacts (package management for dependencies).
Boards facilitate work planning and tracking using various work items and Kanban/Scrum boards.
Azure Boards are used for planning work, managing progress, and tracking tasks, user stories, bugs, epics, and features using Kanban boards, Scrum boards, backlogs, and sprints. It's a key interface for team collaboration on project tasks.
Repos provide Version Control capabilities using Git or Team Foundation Version Control (TFVC).
Azure Repos allows for code management through Version Control systems like Git and TFVC. It supports branching, merging, pull requests, and managing multiple repositories within a project.
Pipelines automate the build, test, and deployment processes for applications (CI/CD).
Azure Pipelines enable Continuous Integration and Continuous Delivery by automating the build, test, and deployment of code. They allow setting rules for deployment across different environments.
Test Plans support both manual and automated testing throughout the development lifecycle.
Azure Test Plans provide tools for planning, executing, and tracking manual and automated tests, ensuring the quality of the software before deployment.
Artifacts manage reusable packages and dependencies from private or public repositories.
Azure Artifacts allows teams to create, host, and share package feeds (like NuGet, npm, Maven) from both private and public repositories, which are essential for application deployment.
Waterfall methodology is traditional, pre-planned, rigid, and risk-prone to cost/time overruns.
The Waterfall method is a traditional, sequential approach where all planning, research, timelines, and cost estimates are done upfront. It offers clarity on roles but is rigid, lacks flexibility for changes, and risks cost and time overruns due to unforeseen issues.
Agile methodology is flexible, iterative, collaborative, and delivers value incrementally through smaller chunks.
Agile methodology involves teams working on smaller product pieces, leading to quicker releases of deliverables. It emphasizes close collaboration between business and development teams, allowing for faster value delivery and stakeholder feedback throughout iterations.
Agile's weakness lies in potential rework due to poor requirement gathering and cost overruns from repeated iterations.
Agile's weaknesses include the risk of multiple iterations and rework if requirement gathering is insufficient, potentially leading to client dissatisfaction and cost overruns. Repeated iterations to fix bugs or address feedback can also increase costs.
Choosing between Waterfall and Agile depends on project needs, as both have pros and cons.
There isn't a universally 'better' methodology; both Waterfall and Agile have advantages and disadvantages. The choice depends on the specific needs, constraints, and context of the project.
Creating an Azure DevOps account involves signing up with a Microsoft account or GitHub.
To create an Azure DevOps account, users can sign up using a Microsoft account or a GitHub account. The process involves providing basic information like project name, visibility, and region.
An Azure DevOps organization is a logical grouping of related projects and a mandatory element for work.
An organization in Azure DevOps serves as a top-level container for organizing and connecting related projects. It's a fundamental requirement for working within Azure DevOps, with a unique name that forms part of the URL.
Azure DevOps organizations must have unique names to avoid ambiguity.
Organization names in Azure DevOps must be unique because they are part of the URL, ensuring no ambiguity when accessing resources.
Azure DevOps allows managing organizations, including creating new ones and configuring settings.
Users can create new organizations in Azure DevOps, distinct from the default one created upon account signup. Organization settings include updating information, managing users, and configuring billing and policies.
Organization settings allow configuration of overview, users, billing, policies, permissions, and integrations.
Within organization settings, users can manage overview details, add/manage users, view billing information (including free tiers for basic users and pipeline minutes), configure global notifications, connect to Azure Active Directory for user management, and set various policies and permissions.
A project in Azure DevOps is a workspace for complete product development, hosting all core services.
A project in Azure DevOps is the central place where a team collaborates to plan, track progress, code, test, and deploy a software solution. It contains all the core Azure DevOps services like Boards, Repos, Pipelines, Test Plans, and Artifacts.
Azure DevOps projects can be either private or public, controlling content visibility and access.
Projects can be either private, requiring users to sign in and be explicitly added for access, or public, visible and accessible to anyone without login. Public projects are typically used for open-source development.
Project settings allow configuration of details, visibility, administrators, services, and deletion.
Project settings include editing project name, description, visibility, managing project administrators, enabling/disabling specific Azure DevOps services for the project, and the option to delete the project.
Each Azure DevOps project automatically includes a default team with the same name.
When a new project is created, a default team is automatically generated with the same name as the project, and the creator is typically added as the initial member.
Teams can be created within projects to manage members and assign responsibilities.
Teams can be created within projects to group members and assign roles. Members can be invited via email, and their access levels (e.g., Basic) are managed within the organization's user settings.
Work item processes (Basic, Agile, Scrum, CMMI) define the types of work items and workflows available in Boards.
The choice of a work item process (like Basic, Agile, Scrum, CMMI) during project creation dictates the available work item types (e.g., Epic, Issue, Task, Bug, Feature, Product Backlog Item) and the workflow states visible in Azure Boards.
Azure Boards provide the interface for managing work items using Kanban and Scrum methodologies.
Azure Boards offer a visual interface (Kanban board, backlog, sprints) to manage and track work items like Epics, Features, Product Backlog Items, Tasks, and Bugs. It supports collaboration and progress tracking for the entire team.
Work items can be added to boards, assigned to users, and categorized by epic or iteration.
Users can add new work items (e.g., Product Backlog Items, Bugs) to the board, assign them to team members, set their status (New, Approved, Committed, Done), and link them to parent epics or specific iterations/sprints.
Repositories (Repos) are essential for Version Control, tracking code changes over time.
Azure Repos provides Version Control capabilities using Git or Team Foundation Version Control (TFVC). It allows teams to manage code history, track changes, revert to previous versions, and collaborate effectively on source code.
Repositories can be cloned locally, imported from other sources, or initialized with README/gitignore.
Users can clone an Azure Repo to their local machine using HTTPS or SSH links, import repositories from other platforms (like GitHub), or initialize a new repository with a README file for project documentation and a .gitignore file to specify untracked files.
Branching in Repos allows parallel development of features, with changes merged via pull requests.
Developers can create branches from the main branch to work on new features independently. Once development is complete, changes are proposed for merging back to the main branch via pull requests, which undergo review to resolve conflicts.
Pull Requests facilitate code review and merging of changes from feature branches into the main branch.
Pull Requests are a mechanism to review code changes from a feature branch before merging them into the main branch. This process helps identify and resolve merge conflicts and ensures code quality.
Cloning an Azure repository locally allows developers to work offline and integrate changes via Git commands.
Azure repositories can be cloned to a local system using the command line (Git Clone). This enables offline work, and changes can be committed and pushed back to the remote repository.
IDEs like Visual Studio can be connected to Azure DevOps repositories for integrated version control.
Integrated Development Environments (IDEs) can connect to Azure DevOps repositories, allowing developers to perform Git operations (fetch, pull, push, commit) directly within the IDE while working on the codebase.
Pipelines automate the build and test process for code, enabling Continuous Integration.
Azure Pipelines automate the build and testing of code whenever changes are committed. This process, known as Continuous Integration (CI), ensures that the codebase remains stable and integrated.
Pipeline configuration involves selecting a template, connecting to a repository, and defining build steps (YAML).
Creating a pipeline involves selecting a template (e.g., C++, ASP.NET), connecting it to the specific repository, and defining the build process steps, often using a YAML file that specifies triggers, pools, and script executions.
Free tier grants for Azure Pipelines allow for limited usage of hosted parallel jobs.
Azure Pipelines offer a free tier for private projects, including a certain number of hosted parallel jobs and minutes per month, which needs to be applied for if not automatically granted.
Release pipelines automate the deployment of built artifacts to various environments.
Release pipelines extend build pipelines by automating the deployment of application artifacts to different environments (e.g., development, staging, production). They define stages, approvals, and tasks for the deployment process.
Artifacts produced by build pipelines are consumed by release pipelines for deployment.
Release pipelines utilize the artifacts generated by build pipelines as their input. These artifacts contain the compiled and packaged application ready for deployment to various environments.
Release pipelines can be configured with stages, triggers (manual/scheduled), and deployment tasks.
Users can define stages within a release pipeline, set up triggers for automated deployments (e.g., on every successful build, or on a schedule), and configure specific tasks for deploying to target environments (like Azure App Service).
Ask a Question
*Uses 1 Wisdom coin from your coin balance
