Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Features
- Improved visibility into YAML pipeline stage dependencies
- New Agent CDN
- Node 16 will be removed from pipelines-* Pipeline agent packages
Improved visibility into YAML pipeline stage dependencies
YAML pipelines provide flexibility for managing complex workflows, but visualizing stage dependencies has been a challenge—especially in multi-region deployments.
It hasn't always been clear how stages are connected. For example, determining whether CUS3 depends on WUS1 in addition to WUS2 and WUS3 has required reviewing the YAML directly.
With this sprint, stage dependencies are now displayed when a stage is expanded, providing immediate insight into execution order and upstream requirements.
New Agent CDN
As Edgio CDN is being retired, the domain URL owned by Edgio https://vstsagentpackage.azureedge.net will also be retired. We're adding a new domain URL https://download.agent.dev.azure.com supported by the new CDN. Be sure to add this new domain URL to your firewall allowlist. Agent package downloads for self-hosted agents will fail once the old domain URL is removed. Refer to the post for more details.
Node 16 will be removed from pipelines-* Pipeline agent packages
Agent tasks can be implemented in PowerShell or Node. The agent ships with multiple versions of Node that tasks can target.
As new Node versions are released, tasks are updated to use new Node versions. The runtimes are included with the agent.
As Node versions exit out of the upstream maintenance window, some Pipelines tasks still depend on it. Azure DevOps updates supported tasks to a supported Node version. Third party tasks may still need older Node versions to run.
To accommodate this, we have two types of Pipeline agent packages:
| Packages | Node versions | Description |
|---|---|---|
vsts-agent-* |
6, 10, 16, 20 | Includes all Node versions that can be used as task execution handler |
pipelines-agents-* |
20 | Includes only recent Node versions. The goal for these packages is to not include any end-of-life version of Node. |
If you want to run a task that requires the Node 16 execution handler on an agent that doesn't have Node 16 bundled, you can install the execution handler by inserting the NodeTaskRunnerInstaller@0 task in your pipeline:
steps:
- task: NodeTaskRunnerInstaller@0
inputs:
runnerVersion: 16
Next steps
Note
These features will roll out over the next two to three weeks.
Head over to Azure DevOps and take a look.
How to provide feedback
We would love to hear what you think about these features. Use the help menu to report a problem or provide a suggestion.
You can also get advice and your questions answered by the community on Stack Overflow.