Azure Devops Project Configuration Settings - Part One

Now it’s time for Azure DevOps.

Components available in Azure DevOps,

Example

To build any application we require proper release plans with the help of team members, like project managers, technical architects, Team Leaders, Developers (Sr. or Jr.), Testers, and Operations teams.

Azure DevOps will help all these factors in a single platform. Start with an idea from scratch. Now we're planning to introduce a new project after discussing with all board members; i.e., planning to release a new product by using our brand.

For this new idea, I have a sales application to monitor sales that are done quarterly, half-yearly, and annually.

The project manager gets the complete requirements for initial deliveries. For initial deliveries, she/he plans for the delivery’s deadlines and commitments for each module sprint level-wise or executes with the help of scrum masters.

Now we'll see how Azure devops will help us here.

Go here and log in with your organization or Microsoft email account. Click on "New Organization" and it is redirected to the URL as shown in the below screenshot. Create a New Organization to create a project and click on Continue.

Now Organization is created as shown in the below screenshot. It’s time to create a new project with your company naming conventions to follow below-steps shown in the screenshot. With one email id, you can create an 'n' number of organizations, and in one organization you can create an 'n' number of projects.

Once you click on the project setting url will be redirected to the below screen.

Overview

1. Name: Name of the project.
2. Description: Description of the project
3. Process: The below processes are supported in Azure DevOps.
   

Basic Process

Below are the Backlog levels in the Basic Process with each work item type and description along with graphical representational UI.

Agile Process

Below are the Backlog levels in Agile Process with each work item type and description along with graphical representational UI.

CMMI Process

Below are the Backlog levels in the CMMI Process with each work item type and description along with graphical representational UI.

Scrum Process

Below are the Backlog levels in the Scrum Process with each work item type and description along with graphical representational UI.

• Visibility: Security information about your project; either you can choose public or private (Protected with selected team members)
• Project Administrators: Give information about administrator details for selected or current open projects.
• Azure DevOps Services: Turning off, and hiding services for all project members. If you choose to enable each service later, all your existing data will be available.
• Visibility: Security information about your project whether it is public or private (Protected with selected team members)
• Project Administrators: Give information about administrator details for selected or current open projects.
• Azure DevOps Services: Turning off services, hides for all members of this project. If you choose to enable this service later, all your existing data will be available.

Teams

In the teams option, we have team information about this project and we can create multiple teams for each project.

For example, I'm creating a new team for pipeline activities.

Permissions

In Permission, we can create multiple groups and users for project requirements by clicking on the New Group button.

Notifications

Manage notifications to the team members and groups configured for the project teams. If any code changes or deployments are done to the project, you can trigger email notifications to your teams. You can set alerts based on your requirements for the current project, a detailed explanation will be available in future articles.

Service hooks

Integrate your favorite notification service for every code change, and build releases according to the list provided by Azure DevOps. A detailed explanation of enabling services will be explained in upcoming articles.

Dashboards

You can provide access to admins for creating, editing, and deleting dashboards team admins by clicking checkboxes as shown in the below screenshot.

Project Configuration

In project configuration, we can plan project sprint plans and create sprints (Iterations planning). More about project configuration in the next articles.

Team Configuration

In team configuration, we can configure the below items for processing (Agile) customization.

1. General
2. Iterations
3. Areas
4. Templates
   

GitHub Connections

You can connect your GitHub project in this section.

Agent Pools

You can create multiple agent pools for your build solutions and deployments but make sure whether or not creating multiple agent pools will exceed your billing. As per usage, you need to create agents for project requirements. More about Azure agent pool information will be available in the next articles.

Parallel Jobs

Creating parallel jobs for your project at the time of build. Current job information for the project is available in this section.

Test Management

We will configure Flaky test management in this section. To learn more about Flaky Test Management go to the below Url.

Url: https://docs.microsoft.com/en-us/azure/devops/pipelines/test/flaky-test-management?view=azure-devops

Release Retention

In this section, we have information about retaining policy settings for releases. We can configure our retention policies in the retention option which is at the bottom of the page.

Service Connections

You can add your services by clicking the New Service Connection option. In the drop down we have multiple information about service connections. To know more about configuring service connections you can refer to the below link to learn more.

Url: https://docs.microsoft.com/en-us/azure/devops/pipelines/library/service-endpoints?view=azure-devops&tabs=yaml

Repositories

In this section, we have the complete information about repositories available and securities and policies for current projects in the organization.

Policies

You can create branch policies for your branches. By clicking on Go to Branches, we can create our own policies for the Agile process or current processes for approving PRs, commits, and gateway for PR (Pull Requests) approvals.

Happy Coding.