-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Comments
Could someone merge-capable merge it? @gep13 could you please? |
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 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 |
As Microsoft explains here the pipelines are being moved to Node 10. The hints in the pipeline also already appear.
A guide for the changeover can be found here.
Since it wasn't too complicated, I started an implementation of the guide.
The text was updated successfully, but these errors were encountered: