azure-pipelines
VSTS use API to set build parameters at queue time
Using the Chrome Developer tools to capture the payload of a Queue action in the web UI, I’d hazard a guess the format you’re looking for is: POST https://dev.azure.com/jessehouwing/6484ebc3-af16-4af9-aa66-6b3398db7214/_apis/build/builds { “queue”: { “id”: 27 }, “definition”: { “id”: 53 }, “project”: { “id”: “6484ebc3-af16-4af9-aa66-6b3398db7214” }, “sourceBranch”: “refs/heads/master”, “reason”: 1, “demands”: [], “parameters”: “{\”system.debug\”:\”true\”,\”DefinedVariable\”:\”Override Value\”}” }
How to get the variable value in TFS/AzureDevOps from Build to Release Pipeline?
The is no official way to pass variables from Build to Release. The only way to accomplish this is to store the values in a file (json, xml, yaml, what have you) and attach that as a Build Artifact. That way you can read the file in the release and set the variable again. Martin … Read more
Build .NET Core 3.0 on Azure Pipelines
You can install the .Net core SDK 3.0 during the pipeline with .Net Core SDK Installer task: – task: UseDotNet@2 displayName: ‘Install .net core 3.0 (preview)’ inputs: packageType: sdk version: ‘3.0.100-preview6-012264’ installationPath: $(Agent.ToolsDirectory)/dotnet I specified the last preview version of .net core sdk 3.0, you can put an earlier version, you can find here the … Read more