You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The best way to implement this would be to persist nrtest benchmark comparison results in a "receipt.json" file that could be parsed on failure post-test. Then the artifacts from failing tests could be easily identified and cached for retrieval.
Created Issue #17 over on the nrtest repo to discuss this with the nrtest developer @davidchall.
bemcdonnell
changed the title
Configure Appveyor to save artifacts from failing tests
Push Build Artifacts AWS-S3
Jan 30, 2018
@bemcdonnell I think it would be a lot easier and more straight forward to just configure the built in facility Appveyor has for saving artifacts and accessing them from the build status page.
On Appveyor it looks like you are able to associate and retrieve artifacts with a CI build.
https://help.appveyor.com/discussions/questions/1649-how-to-keep-a-build-artifact-when-tests-fail
This could be useful for solving build and testing problems on the CI server.
The text was updated successfully, but these errors were encountered: