on 13 Jun, 2019 08:27 PM
Here is how it is configured for our solution. We are building for each check-in both debug and release builds. Now appveyor UI distinguishes the debug and release builds. It appears the view when debug build is clicked is different than the one with release build. Why then should I see two different files as the artifact? I would like to see one artifact produced for each job/build. Same name for the files make more sense to me.
Is this isolation achievable? Not that I can't leave with how it is but it is a bit confusing.
The other alternative for me is to somehow specify a build configuration per Git repo. Say dev branch does the debug build and master does the release build. How do I do that?
on 14 Jun, 2019 07:33 PM
Sorry not quite sure what you mean by deduplicate
We have these two msbuild command lines in project's Build tab settings.
msbuild ApfmWebServices\ApfmServices.csproj /t:Package /p:Configuration=Release /p:PackageLocation=WS3ReleaseBuild.zip /p:PackageAsSingleFile=True
So both the job produces two *.zip files. I am thinking the debug job should build one file and the release job should build another file and there should be only one command line here. The output file can be the same (should be the same in my view).
msbuild ApfmWebServices\ApfmServices.csproj /t:Package /p:Configuration=%configuration%/p:PackageLocation=WS3.zip /p:PackageAsSingleFile=True
It didn't work. Something was wrong with output file.
In the screen shot you are calling the exact same msbuild command for each configuration. If you only want one artifact per configuration then deduplicate (remove one of the commands) and make the confiugration a parameter.
I didn't notice that you have the script set to powershell. In that case replace %configuration% with $env:configuration (the proper powershell syntax for accessing environment variables).