This pull request adds azure-pipelines.yaml configuration to control CI and PR validation. This also adds both debug and release validation. Previously, only the release version was build and tested via CI.
This addition is the bare minimum of the yaml configuration. BuildPlatform has not been added to the configuration yet. I could not make it work together with the dotnet build command. Information on this can be found here: dotnet issue 10421. So currently, the build platform from the project files is used.
I am currently using 'tasks' for the individual steps, but it seems that 'scripts' are generally more popular for dotnet core pipelines. Here is a guide using scripts: yaml-build-pipeline-net-core-azure-devops-tutorial)
Another example is the TorchSharp pipeline, but that also handles additional steps for getting external resources etc.. 'Scripts' definitely seems more flexible than 'tasks', so I might switch to 'scripts' in the future when I have some more experience with them.
This pull request adds
azure-pipelines.yamlconfiguration to control CI and PR validation. This also adds both debug and release validation. Previously, only the release version was build and tested via CI.This addition is the bare minimum of the yaml configuration. BuildPlatform has not been added to the configuration yet. I could not make it work together with the dotnet build command. Information on this can be found here: dotnet issue 10421. So currently, the build platform from the project files is used.
I am currently using 'tasks' for the individual steps, but it seems that 'scripts' are generally more popular for dotnet core pipelines. Here is a guide using scripts: yaml-build-pipeline-net-core-azure-devops-tutorial)
Another example is the TorchSharp pipeline, but that also handles additional steps for getting external resources etc.. 'Scripts' definitely seems more flexible than 'tasks', so I might switch to 'scripts' in the future when I have some more experience with them.