Deprecated Node version in TriggerBuild@4

[chriss5000]

Since this task seems to use Node version 10, there is a warning on pipeline execution:

##[warning]Task 'Trigger Build' version 4 (TriggerBuild@4) is dependent on a Node version (10) that is end-of-life. Contact the extension owner for an updated version of the task. Task maintainers should review Node upgrade guidance: https://aka.ms/node-runner-guidance

Is it possible to updrage Node version for this task in order to resolve the warning?

[huserben]

Hi @DunkleVollNuss

Thanks for the info. I'll upgrade the tasks in the coming weeks. I'll let you know once the new versions are published.

[minuz]

Hi! Firstly, thanks for the great work! Secondly, any news on the node update?

[huserben]

@chriss5000 @minuz I updated the tasks now, the warning should be gone. I ran through all my smoke tests, and everything still works. So I don't expect any issues. It should also still work if you have an "old" node js version - that said ideally you update to the latest agent (that supports node 20).

The tasks should auto-update.

I'll keep this issue open till one of you confirms it works on your end as well.

[dlaw1912]

I've recently updated an agent from v3.227.1 to v4.251.0, and am now seeing this warning message for TriggerBuild@4.1.0.

I see the latest task version should be 4.2.0 - how can I get my pipeline to run that?

[huserben]

@dlaw1912 Are you using Azure DevOps Server?

[dlaw1912]

No, looks like Azure DevOps Service (Version Dev19.M252.1)

[huserben]

@dlaw1912 if you use Azure Devops in the cloud, the task should automatically update, see also the docs:

When a new minor version is released (for example, 1.2 to 1.3), your pipeline automatically uses the new version.

Unless you specify the task version with all 3 segments. If so, then you must adjust your yaml and make sure to use 4.2.0

[dlaw1912]

The YAML only specifies the major version:

- task: TriggerBuild@4

I've tried deleting the TriggerBuild from the agent's _tasks folder, but it still downloads 4.1.0.

[huserben]

Ok, so you use self-hosted agents. Maybe you need to update the agent itself as well as the Node.js that is installed on the agent. It could be that whatever is installed isn't compatible with the new version.