Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Push Build Artifacts AWS-S3 #134

Closed
michaeltryby opened this issue Jan 17, 2018 · 3 comments
Closed

Push Build Artifacts AWS-S3 #134

michaeltryby opened this issue Jan 17, 2018 · 3 comments
Assignees
Labels
Moderate Moderately Challenging Task type:enhancement

Comments

@michaeltryby
Copy link

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.

@michaeltryby
Copy link
Author

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 bemcdonnell changed the title Configure Appveyor to save artifacts from failing tests Push Build Artifacts AWS-S3 Jan 30, 2018
@bemcdonnell bemcdonnell self-assigned this Jan 30, 2018
@bemcdonnell
Copy link
Member

@michaeltryby, I think it would valuable to go ahead an push all artifacts to AWS. I'll work on that soon

@michaeltryby
Copy link
Author

@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.

@bemcdonnell bemcdonnell added the Moderate Moderately Challenging Task label Feb 22, 2018
@bemcdonnell bemcdonnell added this to To do in General Tasks Feb 22, 2018
karosc pushed a commit that referenced this issue Sep 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Moderate Moderately Challenging Task type:enhancement
Projects
General Tasks
  
To do
Development

No branches or pull requests

2 participants