I have not worked on nop-commerce in a while so my build pipeline is out of date...
I am not sure why the nop team chose Travis over AzurePipelines, but I am guessing many users would want to deploy to AzureDevops (like we do)...
First of all, I have generated adjusted the pipeline that generates the build YAML:
pool:
name: Azure Pipelines
steps:
- task: DotNetCoreCLI@2
displayName: 'dotnet restore'
inputs:
command: restore
projects: ./src/NopCommerce.sln
- task: DotNetCoreCLI@2
displayName: 'dotnet build'
inputs:
projects: ./src/NopCommerce.sln
arguments: '--configuration $(BuildConfiguration)'
- task: DotNetCoreCLI@2
displayName: 'dotnet test'
inputs:
command: test
projects: |
./src/Tests/Nop.Core.Tests/Nop.Core.Tests.csproj
./src/Tests/Nop.Web.MVC.Tests/Nop.Web.MVC.Tests.csproj
./src/Tests/Nop.Services.Tests/Nop.Services.Tests.csproj
arguments: '--configuration $(BuildConfiguration) --collect "Code coverage"'
- task: DotNetCoreCLI@2
displayName: 'dotnet publish'
inputs:
command: publish
arguments: '--configuration $(BuildConfiguration) --output $(Build.ArtifactStagingDirectory)'
- task: PublishBuildArtifacts@1
displayName: 'Publish Artifact'
inputs:
ArtifactName: '$(Parameters.ArtifactName)'
something like this could be added to the file
azure-pipelines.ymlin root of the project if using a private GitHub account connected to Azure DevOps (VisualStudio Online) build pipeline.
I plan on looking at making code coverage work in the interface soon and https://stackoverflow.com/questions/60893419/azure-devops-code-coverage-for-net-core-3-1 seems to show the way. I will update the above if required...
Next will be the release pipeline...