Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating Node in the Azure Pipelines agent #72

Open
JuergenRB opened this issue Nov 29, 2021 · 4 comments · May be fixed by #73
Open

Updating Node in the Azure Pipelines agent #72

JuergenRB opened this issue Nov 29, 2021 · 4 comments · May be fixed by #73

Comments

@JuergenRB
Copy link

As Microsoft explains here the pipelines are being moved to Node 10. The hints in the pipeline also already appear.

image

A guide for the changeover can be found here.
Since it wasn't too complicated, I started an implementation of the guide.

@JuergenRB JuergenRB linked a pull request Nov 29, 2021 that will close this issue
@mitoihs
Copy link

mitoihs commented Feb 28, 2022

Could someone merge-capable merge it? @gep13 could you please?

@m-soltani
Copy link

This issue still persists and since Node 6 has reach of EoL, I am interested to know If they are plans to update task's node version

image

@devlead
Copy link
Member

devlead commented Dec 6, 2024

ATM the plan is probably to depreciate this extension as it's based on the old Cake.exe which is no longer supported.

The recommended way instead would be to use Cake.Tool and pin its version using a .NET tool manifest, all need to bootstrap Cake then would be an Azure Pipelines yaml like below

jobs:
  - job:
    steps:
    - script: |
        dotnet tool restore
        dotnet cake --target=AzurePipelines
      displayName: Run Cake Script

The above assumes you've got a target called AzurePipelines.

Make sure to have a tool manifest available in your repository or create one using the following command in repo root:

dotnet new tool-manifest

Install Cake as a local tool using the dotnet tool command:

dotnet tool install Cake.Tool --version 5.0.0

You can replace 5.0.0 with a different version of Cake you want to use.

@m-soltani
Copy link

ATM the plan is probably to depreciate this extension as it's based on the old Cake.exe which is no longer supported.

The recommended way instead would be to use Cake.Tool and pin its version using a .NET tool manifest, all need to bootstrap Cake then would be an Azure Pipelines yaml like below

jobs:
  - job:
    steps:
    - script: |
        dotnet tool restore
        dotnet cake --target=AzurePipelines
      displayName: Run Cake Script

The above assumes you've got a target called AzurePipelines.

Make sure to have a tool manifest available in your repository or create one using the following command in repo root:

dotnet new tool-manifest

Install Cake as a local tool using the dotnet tool command:

dotnet tool install Cake.Tool --version 5.0.0

You can replace 5.0.0 with a different version of Cake you want to use.

I would still would wait to see if the implementation details like above can be masked by developing/upgrading the Cake@2 version. otherwise, this would be something that our internal team needs to implement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants