I seem to be missing something. When creating a build pipeline with the classic editor I can see an artifacts tab on the top right:
There I can browse what the compiler created, helping to find out the folder structure for the release pipeline.
Now when I create a build pipeline with the YAML template (also NET Framework) there is no such thing as Artifacts:
According to the logs, some files have been written. Is there some kind of browser for files, or do I have to guess which of these variables match to which folder in the logfiles?
This is how my summary page looks like:
This is the YAML:
# .NET Desktop
# Build and run tests for .NET Desktop or Windows classic desktop solutions.
# Add steps that publish symbols, save build artifacts, and more:
# https://docs.microsoft.com/azure/devops/pipelines/apps/windows/dot-net
trigger:
- master
pool:
vmImage: 'windows-latest'
variables:
solution: '**/*.sln'
buildPlatform: 'Any CPU'
buildConfiguration: 'Release'
steps:
- task: NuGetToolInstaller@1
- task: NuGetCommand@2
inputs:
restoreSolution: '$(solution)'
- task: VSBuild@1
inputs:
solution: '$(solution)'
platform: '$(buildPlatform)'
configuration: '$(buildConfiguration)'
- task: ArchiveFiles@2
inputs:
rootFolderOrFile: '$(Build.BinariesDirectory)'
includeRootFolder: false
archiveType: 'zip'
archiveFile: '$(Build.ArtifactStagingDirectory)/Release.zip'
replaceExistingArchive: true
The YAML i use is mostly the standard YAML produced when building from a Github Repository. Does this affect if i can see Artifacts? Should i somehow copy the Github content to Azure first and then build it?