Home → Problems →

Error in PushArtifact command in build script not detected as error, does not stop build

• Edit

Scott

03 Feb, 2015 07:25 PM

I have a manual build script that pushes artifacts. When it errors, the errors are not detected and the build script just keeps plugging along. I would expect any errors in the build script to stop the build.

Example Script:
msbuild API\API.csproj /t:Package /p:PackageLocation=API_WAP.zip /p:Configuration=Release
appveyor PushArtifact API_WAP.zip
msbuild Site\Site.csproj /t:Package /p:PackageLocation=Site_WAP.zip /p:Configuration=Release

Output:
[Build output excluded]
appveyor PushArtifact API_WAP.zip [Note: I did not fully qualify the location]
Error pushing artifact: File not found: C:\projects\API_WAP.zip
[Note, the build does not stop here, it just keeps plugging on]
msbuild Site\Site.csproj /t:Package /p:PackageLocation=Site_WAP.zip
Microsoft (R) Build Engine version 12.0.31101.0
[Microsoft .NET Framework, version 4.0.30319.34209]
Copyright (C) Microsoft Corporation. All rights reserved.
Build started 2/3/2015 7:12:47 PM.
...

1. Support Staff 1 Posted by Feodor Fitsner on 03 Feb, 2015 07:43 PM

   

   Good catch - will fix that!

   • Edit

2. Support Staff 2 Posted by Feodor Fitsner on 05 Feb, 2015 05:20 AM

   

   It's been fixed - now it exists with non-zero code if there are any errors.

   • Edit

3. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:53 AM.