Store some artifacts in case of failure

Kirill Müller's Avatar

Kirill Müller

24 Sep, 2015 12:54 PM

(Already reported at https://github.com/appveyor/ci/issues/401)

Would you consider making artifacts available even in case of a build failure? In our case, some artifacts are log files which contain important information about the build failure. The current workaround is to print the contents of the logs, but this clutters the output.

I know I can push the artifacts manually via the API, but I think it would be much simpler to have a configuration option that allows an artifact to be published even if the build failed.

artifacts:
  - path: '*.Rcheck\**\*.log'
    name: Logs
    publish_on_failure: true

See also https://github.com/krlmlr/r-appveyor/issues/37

Thanks!

  1. Support Staff 1 Posted by Feodor Fitsner on 26 Sep, 2015 08:13 PM

    Feodor Fitsner's Avatar

    Sure, this could be added.

    Anyway, pushing artifacts on error is just a few lines in appveyor.yml, for example:

    on_failure:
    - appveyor PushArtifact npm-debug.log
    
  2. 2 Posted by Kirill Müller on 26 Sep, 2015 09:12 PM

    Kirill Müller's Avatar

    Thanks, I appreciate it very much. Looking forward to it.

    I'm aware of PushArtifact, but it's a complicated path in my case (as in the example I posted).

  3. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:00 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