Notikumi
Veidojiet inteliģentas lietotnes
17. marts 21 - 21. marts 10
Pievienojieties meetup sērijai, lai kopā ar citiem izstrādātājiem un ekspertiem izveidotu mērogojamus AI risinājumus, kuru pamatā ir reālas lietošanas gadījumi.
Reģistrēties tūlītAzure DevOps integration of services overview
Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019
With Azure DevOps, you can connect to and collaborate across its core services. You can use various features to link and track your devops tasks across Azure Boards, Azure Repos, Azure Pipelines, and Azure Test Plans. This article shows you options for how to use the cross-service integration of Azure DevOps to improve your workflow and productivity.
Links to more information:
The following table summarizes some of the features that help you work with your team and other teams.
| Feature | Description |
|---|---|
@mentions (add to discussions and comments) |
You can @mention a team member or an entire team within a work item form discussion or the comment section of a commit, pull request, or changeset. |
#ID (link to a work item) |
To support end-to-end traceability, you can link to work items from commits, pull requests, and changesets. |
| Teams | Each team gets access to a suite of Agile tools and team assets. These tools let teams work autonomously and collaborate with other teams across the enterprise. Each team can configure and customize each tool to support how they work. For quick navigation, they can favorite repositories, pipelines, and test plans. |
| Alerts | Configure or opt out of personal, team, project, or organization-level alerts. Subscribe to email alerts when changes occur to work items, code reviews, pull requests, source control files, builds, and more. |
| Summaries by email | - Email a list of work items - Email query items - Send release summaries by email |
| Wiki | Embed Azure Boards query results in Wiki. |
You can link code changes to user stories and features with different link types. For Git, use Branch, Commit, Pull Request, or Tag. For TFVC, use Changeset or Versioned Item.
The following table summarizes the integration points between Azure Boards and Azure Repos.
| Feature | Description |
|---|---|
| Drive Git development from work items | You can initiate a Git branch or link to Git commits or pull requests and drive your Git development cycle for a work item from within the work item form. |
| Automatically link and transition work items with Git commits | For a Git repository, you can turn on or off the following options: - Close work items with mentions in commit comments. - Remember user choices for completing work items with pull requests. - Link work items from commit comments. You can also automate linking from commits or pull requests in repo settings. - Commit mention linking: Turn on to link commits to work items with #WorkItemID in commit messages. Turn off when you push a repo from a different account or service. Azure DevOps automatically turns off this feature when you import a repo. - Commit mention work item resolution: Turn on to close work items with Fixes #WorkItemID in commits. - Work item transition preferences: On by default, it remembers each user’s option to complete linked work items with pull requests. You can turn this feature off to discourage users from completing work items with pull requests. When it's off, users have to choose to complete work items for each pull request. |
| Check for linked work items in a Git branch | Encourage traceability by checking for linked work items on pull requests. |
| Auto complete work items with pull requests | When you link a work item to a pull request (PR), you can automatically complete those work items when you successfully complete the PR. The system defaults to your selection for future PRs. |
| View list of code objects a single work item is linked to | You can link work items to code changes, builds, and releases—providing an audit trail of the feature development. |
| Query for external links | You can query for work items that contain links to branches, commits, pull requests, or tags. |
| Configure branch policies to support work tracking | To ensure that changes to a branch have links to work items, you configure the branch policy for a Git repository in repo settings. Turn on the Check for linked work items option. Choose Required to mandate all pull requests have at least one linked work item in order to be completed. Choose Optional to allow pull requests without linked work items, but warn about it. |
The following table summarizes the integration points between Azure Boards and Azure Pipelines. Several features provide support for end-to-end traceability as user stories and features move through the development cycle. As with Azure Repos, you can link work items to pipeline objects with the following link types: Build, Integrated in build, and Integrated in release.
Feature
Description
Manually link work items to builds.
Link work items to builds in the same or other project within the organization or collection.
Link work items to builds in the same project within the organization or collection.
Set integration option to automatically create Integrated in build links to work items linked to a branch, commit, or pull request associated with a pipeline.
Required to populate the Development control with Integrated in build links. The work items or commits that are part of a release are computed from the versions of artifacts. For example, each build in Azure Pipelines is associated with a set of work items and commits. For more information, see Configure pipelines to support integration.
To link work items to builds and releases, choose an option and a branch for a Classic or YAML pipeline. This action creates Integrated in build and Integrated in release stage links for work items that are linked to a branch, commit, or pull request.
Required to populate the work item form Development control with Integrated in build links and the Deployment control with Integrated in release stage links when running a Classic or YAML pipeline. For more information, see Configure pipelines to support integration.
Set integration option to automatically create Integrated in release stage links to work items linked to a branch, commit, or pull request associated with a release.
Required to populate Deployment control in work item form with Integrated in release stage links. For more information, see Release pipelines, How do I integrate and report release status?.
View list of work items linked to a Classic release pipeline
Lists all work items linked to a build or release.
View and open list of work items linked to a Classic or YAML pipeline.
Lists all work items linked to a release since the previous selected release. Can sort the list by each column.
View list of build or release objects a single work item is linked to
You can link work items to builds and releases—providing an audit trail of the feature development and deployment.
Query for external links.
View and quickly navigate to release stages a work item is linked to.
The Deployment control on the work item form shows the stages that the work item is linked to. You can see the status of some runs and open each stage or run by expanding a stage. For more information, see Link and view work items to deployments.
Create a work item on failure, optionally set values for a work item field (Classic)
Create a work item on failure (Classic or YAML), optionally set values for a work item field (Classic)
Automatically create a work item and set fields when a build fails. For more information, see Build options for Classic pipelines, and Customize pipelines, Create work item on failure.
Query Work Items task. Ensure the number of matching work items returned from a query is within a threshold.
Use this task to ensure the number of matching items returned by a work item query is within the configured thresholds. For more information, see Query Work Items task, Control deployments with gates and approvals.
Azure Pipelines provides support for building code stored in Azure Repos, either a Git or Team Foundation Version Control (TFVC) repository. Other repositories that Azure Pipelines supports are listed in Supported source repositories.
The following table summarizes the integration features between Azure Repos and Azure Pipelines.
| Feature | Description |
|---|---|
| Report deployment status | Indicates the status of a deployment on the Files, Commits, and Branches pages for Git repositories. This feature improves the traceability from code commit to deployment. You can configure the release environments to report deployment status. |
| Release status badge | Post the status of your most recent pipeline build in your repository. |
| Code coverage | Publish and review code coverage results that indicate the proportion of your project's code that is actually being tested. |
| Feature | Description |
|---|---|
| Report deployment status | Indicates the status of a deployment on the Files, Commits, and Branches pages for Git repositories. This feature improves the traceability from code commit to deployment. You can configure the release environments to report deployment status. |
| Code coverage | Publish and review code coverage results that indicate the proportion of your project's code that is actually being tested. |
Several collaboration scenarios are supported through Azure Boards work item types. You can use managed queries and the Azure DevOps search function to find and list work items.
Piezīme
You should create some work item types—such as Feedback Request, Code Review Request, Shared Steps, and Shared Parameters—through specific tools or forms. These types get added to the Hidden Types category and don't appear in the menus used to add work items.
For the Inherited process model, you can only customize the following work item types: Test Plan, Test Suite, and Test Case.
| Scenario | Work item type | Description |
|---|---|---|
| Request code review | Code Review Request | Tracks information entered into the TFVC New Code Review form. For more information, see Get your code reviewed with Visual Studio. |
| Provide code review | Code Review Response | Tracks review comments provided by code reviewers in response to a code review request. |
| Request feedback | Feedback Request | Tracks information entered into a request feedback form. Use the following forms to initiate a feedback request. - Request stakeholder feedback - Get feedback. |
| Provide feedback | Feedback Review | Lets stakeholders provide feedback based on requests for feedback or by volunteering feedback using the Microsoft Test & Feedback Marketplace extension. |
| Manual testing | Test Plan | Groups one or more test suites and individual test cases together. Test plans include static test suites, requirement-based suites, and query-based suites. To get started, see Create test plans and test suites. |
| Manual testing | Test Suite | Groups one or more test cases into separate testing scenarios within a single test plan. Grouping test cases makes it easier to see which scenarios are complete. |
| Manual testing | Test Case | Defines steps used to validate individual parts of your code to ensure your code works correctly, has no errors, and meets business and customer requirements. You can add individual test cases to a test plan without creating a test suite. More than one test suite or test plan can refer to a test case. You can effectively reuse test cases without having to copy or clone them for each suite or plan. |
| Manual testing | Shared Steps | Enables sharing steps across several test cases. |
| Manual testing | Shared Parameters | Enables repeating the same test cases with different data. |
Work item types that support the test experience are linked together using the link types shown in the following image. These types include Tested By/Tests, Test Cases/Shared Steps, and Reference By/References.
You can use the web portal to see the test cases that are defined for a test suite, and the test suites that are defined for a test plan. But, there's no specific link type that connects these objects to each other.
The Bug work item type supports the following integrations that you should be aware of when you're tracking bugs.
| Scenario | Description |
|---|---|
| Create a bug from a testing tool | You can add a bug from Test Runner or the Test & Feedback extension. For more information, see Define, capture, triage, and manage bugs. |
| Create inline tests linked to bugs or user stories | When your team tracks bugs as requirements, you can use the board to add tests to verify bug fixes or user stories. |
| Track build information with bugs | The Bug work item form contains System Info, Found in Build, and Integrated in Build, which support tracking code defects found and resolved within pipeline builds. For more information, see Query based on build and test integration fields. |
Azure Test Plans is fully integrated with Azure Pipelines to support testing within continuous integration/continuous deployment (CI/CD). You can associate test plans and test cases with build or release pipelines. Add pipeline tasks to pipeline definitions to capture and publish test results. Review test results via built-in progress reports and pipeline test reports. The following table summarizes the integration points between Azure Pipelines and Azure Test Plans.
| Feature | Description |
|---|---|
| Test plans setting | With test plan settings, you can configure the Test Run settings to associate build or release pipelines and Test Outcome settings. |
| Pipeline test-enable tasks | Specify test-enable tasks within a pipeline definition. Azure Pipelines provides several tasks, including the following tasks, that support a comprehensive test reporting and analytics experience. - Publish Test Results task: Use to publish test results to Azure Pipelines. - Visual Studio Test task: Use to run unit and functional tests (Selenium, Appium, Coded UI test, and more) using the Visual Studio Test Runner. - .NET Core CLI task: Use to build, test, package, or publish a dotnet application. For other tasks, see Publish Test Results task |
| Run automated tests in build pipelines | Associate test plans with a build pipeline so that they run with each build. |
| Associate automated tests with test cases | Associate automated tests with test cases. |
| Set retention policy for automated test results associated with builds | You can set the test retention policy for automated builds from the Pipelines > Retention page. |
| Requirements traceability | The Requirements quality widget supports tracking quality continuously from a build or release pipeline. The widget shows the mapping between a requirement and latest test results executed against that requirement. It provides insights into requirements traceability. |
| Test results trend | The Test results trend configurable widget displays the trend of test results for the selected build or release pipeline. The widget helps you visualize the test trends over a period of time, surfacing patterns about test failures, test duration, and so on. For more information, see Configure the Test Results Trend (Advanced) widget |
| Deployment status | The Deployment status configurable widget shows a combined view of the deployment status and test pass rate across multiple environments for a recent set of builds. You configure the widget by specifying a build pipeline, branch, and linked release pipelines. To view the test summary across multiple environments in a release, the widget provides a matrix view of each environment and corresponding test pass rate. See Associate automated tests with test cases |
| View test results in builds and releases | Both build and release summaries provide details of test execution. Review these summaries to assess pipeline quality, review traceability, and troubleshoot failures. Choose Test summary to view the details in the Tests tab. |
| Test analytics for builds | Each build summary includes an Analytics tab that hosts the Test analytics report. |
Dashboards provide an easy way to monitor progress and status. Teams can add configurable widgets to support their goals. The Analytics service is the reporting platform for Azure DevOps, and replaces the previous platform based on SQL Server Reporting Services. Analytics is optimized for fast read-access and server-based aggregations and provides the following benefits:
- Analytics widgets that you can add to your dashboards
- In-context Analytics reports available from select Azure DevOps pages
- Rollup bars and counts for Azure Boards backlogs
- Custom reports you can create using Power BI
- Custom reports you can create using OData queries
- Support to develop and add your custom Analytics widgets you can add to dashboards
You can add the following built-in widgets to your dashboard. They're organized under the service they support. You might find more widgets from the Azure DevOps Marketplace.
Analytics provides the reporting platform for Azure DevOps. For information, see Data available from Analytics.
Microsoft products support automation or integration with several other applications and services. For more information, see the following articles.
Piezīme. Autors izveidoja šo rakstu ar AI palīdzību. Uzzināt vairāk
Papildu resursi
Apmācība
Mācību ceļš
Use advance techniques in canvas apps to perform custom updates and optimization - Training
Use advance techniques in canvas apps to perform custom updates and optimization
Sertifikācija
Microsoft Certified: Power Automate RPA Developer Associate - Certifications
Demonstrate how to improve and automate workflows with Microsoft Power Automate RPA developer.
Dokumentācija
-
Project summary page, view project activity - Azure DevOps
Learn how to view and update your project summary page to share project vision, objectives, and activity for Azure DevOps.
-
Collaborate on software development through source control, work tracking, and continuous integration and delivery, both on-premises and in the cloud!
-
Delete, remove, restore project - Azure DevOps
Delete or remove a project from your organization in Azure DevOps. Restore a recently deleted project.