|
1 | 1 | --- |
2 | 2 | title: What is Azure Pipelines? |
3 | | -description: Learn how to automatically build, test, and deploy your code with Azure Pipelines |
| 3 | +description: Learn how Azure Pipelines can use continuous integration, testing, and delivery to automatically build, test, and deploy your code. |
4 | 4 | ms.topic: overview |
5 | | -ms.date: 07/01/2024 |
| 5 | +ms.date: 07/24/2025 |
6 | 6 | monikerRange: '<= azure-devops' |
| 7 | +# customer intent: As a developer, I want to learn about Azure Pipelines capabilities so I can automatically build, test, and deliver my code. |
| 8 | + |
7 | 9 | --- |
8 | 10 |
|
9 | 11 | # What is Azure Pipelines? |
10 | 12 |
|
11 | 13 | [!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)] |
12 | 14 |
|
13 | | -Azure Pipelines is the part of Azure DevOps that automatically builds, tests, and deploys code projects. Azure Pipelines combines [continuous integration](#continuous-integration), [continuous testing](#continuous-testing), and [continuous delivery](#continuous-delivery) to build, test, and deliver your code to any destination. Azure Pipelines supports all major languages and project types. |
| 15 | +Azure Pipelines is the part of Azure DevOps that combines [continuous integration](#continuous-integration), [continuous testing](#continuous-testing), and [continuous delivery](#continuous-delivery) to automatically build, test, and deploy code projects to any destination. Azure Pipelines supports all major languages and project types, and can automate workflows in your chosen technologies and frameworks whether your app is on-premises or in the cloud. |
14 | 16 |
|
15 | 17 | :::image type="content" source="media/pipelines-overview.png" alt-text="Screenshot of Azure Pipelines overview."::: |
16 | 18 |
|
17 | 19 | ## Azure Pipelines benefits |
18 | 20 |
|
19 | | -Azure Pipelines provides a quick, easy, and safe way to automate building your projects with consistent and quality code that's readily available to users. |
| 21 | +Azure Pipelines provides a quick, easy, and safe way to automate building your projects with consistent, high-quality, readily available code. |
20 | 22 |
|
21 | 23 | Azure Pipelines offers the following benefits: |
22 | 24 |
|
23 | | -- Works with any language or platform. |
24 | | -- Deploys to different types of targets at the same time. |
25 | | -- Integrates with Azure deployments. |
26 | | -- Builds on Windows, Linux, or Mac machines. |
27 | | -- Integrates with GitHub. |
28 | | -- Works with open-source projects. |
| 25 | +- Deploys to different types of targets simultaneously |
| 26 | +- Integrates with Azure deployments |
| 27 | +- Integrates with GitHub |
| 28 | +- Works with any language or platform |
| 29 | +- Works on Windows, Linux, or Mac machines |
| 30 | +- Works with open-source projects |
29 | 31 |
|
30 | 32 | ## Prerequisites |
31 | 33 |
|
32 | 34 | To use Azure Pipelines, you must: |
33 | 35 |
|
34 | | -- Have an Azure DevOps organization. If you don't have one, you can [create an organization](../../organizations/accounts/create-organization.md). |
| 36 | +- Have an Azure DevOps organization. If you don't have one, [create an organization](../../organizations/accounts/create-organization.md). |
35 | 37 | - Store your source code in a [version control system](#version-control-systems). |
36 | 38 | ::: moniker range="< azure-devops" |
37 | 39 | - Download a [build agent](../agents/windows-agent.md) and install it on a build server. |
38 | 40 | ::: moniker-end |
39 | 41 |
|
40 | 42 | ## Languages and applications |
41 | 43 |
|
42 | | -Azure Pipelines offers tasks to build, test, and deploy Node.js, Python, Java, PHP, Ruby, C#, C++, Go, XCode, .NET, Android, and iOS applications. You can run these apps in parallel on Linux, macOS, and Windows. |
| 44 | +Azure Pipelines tasks can build, test, and deploy applications written in Node.js, Python, Java, PHP, Ruby, C#, C++, Go, XCode, .NET, Android, and iOS. You can run these apps in parallel on Linux, macOS, and Windows. |
43 | 45 |
|
44 | | -There are tasks to run tests in many testing frameworks and services. You can also run command line, PowerShell, or shell scripts in your automation. |
| 46 | +Azure Pipelines offers test tasks in many different testing frameworks and services. You can use command line, PowerShell, or Bash shell scripts to run your automation. |
45 | 47 |
|
46 | 48 | ## Continuous integration |
47 | 49 |
|
48 | | -Continuous integration (CI) is a practice development teams use to automate merging and testing code. CI helps to catch bugs early in the development cycle, making them less expensive to fix. |
| 50 | +Development teams use CI to automate merging and testing code. The CI process helps to catch bugs early in the development cycle so they're easier to fix. |
49 | 51 |
|
50 | | -To ensure quality, Azure Pipelines executes automated tests as part of the CI process. Azure Pipelines CI systems produce artifacts and feed them to release processes to drive continuous deployments. |
| 52 | +To help preserve quality, Azure Pipelines runs automated tests as part of the CI process. Azure Pipelines CI systems produce artifacts and feed them to release processes to drive continuous deployments. |
51 | 53 |
|
52 | 54 | ::: moniker range="< azure-devops" |
53 | | -The Build service in [Azure DevOps Server](https://azure.microsoft.com/services/devops/server/) helps you set up and manage CI for your applications. |
| 55 | +The [Azure DevOps Server](https://azure.microsoft.com/services/devops/server/) Build service helps you set up and manage CI for your applications. |
54 | 56 | ::: moniker-end |
55 | 57 |
|
56 | 58 | ### Version control systems |
57 | 59 |
|
58 | | -Azure Pipelines requires your source code to be in a version control system. Azure Pipelines supports several forms of version control, including [Azure Repos Git, GitHub, and TFVC](../repos/index.md). You can set up Azure Pipelines to automatically build and validate any changes you push to your version control repository. |
| 60 | +Azure Pipelines requires source code to be in a version control system. You can set up Azure Pipelines to automatically build and validate changes you push to your version control repository. |
59 | 61 |
|
60 | | -## Continuous testing |
| 62 | +Azure Pipelines supports several forms of version control, including GitHub and Azure Repos. For more information, see [Supported source repositories](../repos/index.md). |
61 | 63 |
|
62 | | -Azure Pipelines can automate build-deploy-test workflows in your chosen technologies and frameworks, whether your app is on-premises or in the cloud. You can [test your changes continuously](../ecosystems/dotnet-core.md#run-your-tests) in a fast, scalable, and efficient manner. Continuous testing lets you: |
| 64 | +## Continuous testing |
63 | 65 |
|
64 | | -- Maintain quality and find problems during development. You can find problems earlier by running tests automatically with each build, ensuring your app still works after every checkin and build. |
| 66 | +Azure Pipelines continuous testing lets you: |
65 | 67 |
|
66 | | -- Use any test type and test framework. Choose your preferred test technologies. |
| 68 | +- Use any test type and test framework in your preferred test technologies. |
| 69 | +- Test your changes in a fast, scalable, and efficient manner. |
| 70 | +- Find problems earlier during development. Running tests automatically with each build ensures that your app still works after every checkin. |
| 71 | +- View rich analytics and reporting. Review detailed, customizable test results to resolve issues and monitor the quality of your app. Track the health of your builds with actionable build-on-build reports. |
67 | 72 |
|
68 | | -- View rich analytics and reporting. When your build is done, you can review your test results to resolve any issues. Actionable build-on-build reports let you instantly see if your builds are getting healthier. Detailed and customizable test results measure the quality of your app. |
| 73 | +For more information, see [Run tests in parallel for any test runner](../test/parallel-testing-any-test-runner.md). |
69 | 74 |
|
70 | 75 | ## Continuous delivery |
71 | 76 |
|
72 | 77 | Continuous delivery (CD) is the process of building, testing, and deploying code to one or more test or production environments. Deploying and testing in multiple environments optimizes quality. |
73 | 78 |
|
74 | | -Azure Pipelines CD systems produce deployable artifacts, including infrastructure and apps. Automated release processes consume these artifacts to release new versions and fixes to existing systems. Systems that continually monitor and send alerts drive visibility into the CD process. |
| 79 | +Azure Pipelines CD produces deployable artifacts, including infrastructure and apps. Automated release processes consume these artifacts to release new versions or fixes to existing systems. Systems that continually monitor and send alerts allow visibility into the CD process. |
75 | 80 |
|
76 | 81 | ### Deployment targets |
77 | 82 |
|
78 | | -Use Azure Pipelines to deploy your code to multiple targets. Targets include virtual machines, environments, containers, on-premises and cloud platforms, and platform-as-a-service (PaaS) services. You can also publish your mobile application to a store. |
| 83 | +You can use Azure Pipelines to deploy your code to multiple targets. Targets include virtual machines, environments, containers, on-premises and cloud platforms, and platform-as-a-service (PaaS) services. You can also publish your mobile application to a store. |
79 | 84 |
|
80 | | -Once you have CI in place, you can create a release definition to automate the deployment of your application to one or more environments. The automation process is defined as a collection of tasks. |
| 85 | +Once you have CI running, you can create release definitions to automate deploying your application to one or more environments as a collection of tasks. |
81 | 86 |
|
82 | 87 | ## Package formats |
83 | 88 |
|
84 | | -To produce packages that external users can consume, you can integrate package management into your CI/CD pipelines. You can publish NuGet, npm, Maven, or Python packages as artifacts to the built-in Azure Pipelines package management repository, or any other package management repository you choose. For more information about Azure Artifacts, see [Artifacts in Azure Pipelines](../artifacts/artifacts-overview.md). |
| 89 | +To produce packages that external users can consume, you can integrate package management into your CI/CD pipelines. You can publish NuGet, npm, Maven, or Python package artifacts to the built-in Azure Pipelines package management repository, or to any other package management repository you choose. For more information about Azure Artifacts, see [Artifacts in Azure Pipelines](../artifacts/artifacts-overview.md). |
85 | 90 |
|
86 | 91 | ## Azure Pipelines pricing |
87 | 92 |
|
88 | 93 | ::: moniker range=">= azure-devops" |
89 | | -If you use public projects, Azure Pipelines is free, but you need to [request the free grant of parallel jobs](https://aka.ms/azpipelines-parallelism-request). Existing organizations and projects don't need to request this grant. For more information, see [What is a public project](../../organizations/projects/about-projects.md). |
90 | 94 |
|
91 | | -If you use private projects, you can run up to 1,800 minutes or 30 hours of pipeline jobs free every month. |
| 95 | +Azure DevOps grants a free tier of parallel jobs to every organization for both Microsoft-hosted and self-hosted private and public projects. For private projects, the free tier provides one parallel job that can take up to 60 minutes to run, up to 1,800 minutes per month. For public projects, the free grant provides one parallel job with unlimited minutes for self-hosted agents, or up to 10 parallel jobs for Microsoft-hosted projects. |
| 96 | + |
| 97 | +Public projects and some private projects in new Azure DevOps organizations don't automatically get the free grant of parallel jobs by default. You need to request the free grant of parallel jobs by completing the [Azure DevOps Parallelism Request](https://aka.ms/azpipelines-parallelism-request). The request can take several business days to process. |
| 98 | + |
| 99 | +If the free tier of parallel jobs isn't sufficient for your project, you can purchase more capacity per parallel job or [buy more parallel jobs](../licensing/concurrent-jobs.md?tabs=self-hosted#how-do-i-buy-more-parallel-jobs). Paid parallel jobs can take up to 360 minutes to run and have no monthly time limit. |
92 | 100 |
|
93 | | -For more information, see [Pricing based on parallel jobs](../licensing/concurrent-jobs.md) |
94 | | -and [Pricing for Azure DevOps Services](https://azure.microsoft.com/pricing/details/devops/azure-devops-services/). |
| 101 | +For more information, see: |
| 102 | +- [Use private and public projects](../../organizations/projects/about-projects.md#use-private-and-public-projects) |
| 103 | +- [Configure and pay for parallel jobs](../licensing/concurrent-jobs.md) |
| 104 | +- [Pricing for Azure DevOps](https://azure.microsoft.com/pricing/details/devops/azure-devops-services/) |
95 | 105 |
|
96 | 106 | ::: moniker-end |
97 | 107 |
|
98 | 108 | ::: moniker range="< azure-devops" |
99 | | -For five or fewer active users, [Azure DevOps Express](https://azure.microsoft.com/services/devops/server/) is free, simple to set up, and installs on both client and server operating systems. It supports all the same features as Azure DevOps Server 2019. |
| 109 | +For five or fewer active users, [Azure DevOps Express](https://azure.microsoft.com/services/devops/server/) supports all the same features as Azure DevOps Server. Azure DevOps Express is free, simple to set up, and installs on both client and server operating systems. |
100 | 110 |
|
101 | 111 | For more information, see [Pricing for Azure DevOps Server](https://azure.microsoft.com/pricing/details/devops/server/). |
102 | 112 |
|
|
0 commit comments