Attempt to add artifacts whether build is successful or not

ferventcoder's Avatar

ferventcoder

20 Jan, 2015 01:28 PM

The artifacts we use are actually very useful on a failed build.

Note what we get on a successful build - https://ci.appveyor.com/project/ferventcoder/choco/build/1.0.0.25/a...
However, those artifacts that could lead us to discovery of what is wrong are not there on a failed build - https://ci.appveyor.com/project/ferventcoder/choco/build/1.0.0.28/a...

Is there a setting I missed somewhere? :)

  1. 1 Posted by ferventcoder on 20 Jan, 2015 01:47 PM

    ferventcoder's Avatar

    This seems somewhat related to http://help.appveyor.com/discussions/questions/328-recognizing-test... (but different enough to stand out on its own).

  2. Support Staff 2 Posted by Feodor Fitsner on 20 Jan, 2015 05:17 PM

    Feodor Fitsner's Avatar

    You should push them on_finish phase using command-line or PowerShell: http://www.appveyor.com/docs/build-worker-api#push-artifact

  3. 3 Posted by ferventcoder on 20 Jan, 2015 05:36 PM

    ferventcoder's Avatar

    That's one way to do it. :) Thanks for pointing that out. Perhaps a bit of documentation on that then? It varies from other CI systems, they publish artifacts even when builds fail.

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

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac

Recent Discussions

16 Jul, 2019 04:51 AM
15 Jul, 2019 06:33 PM
15 Jul, 2019 06:09 PM
15 Jul, 2019 05:53 PM
15 Jul, 2019 05:46 PM