-
Notifications
You must be signed in to change notification settings - Fork 18
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
CI-agnostic way to display logs on failure #19
Comments
Push artifacts to an orphan branch, tag it, print link to console. |
Can be achieved (mostly) with existing code, create a demo package to illustrate this.
Orphan branches are problematic because they will be downloaded by default when the user does |
Do we really want this? Aren't we fine with uploading artifacts to the CI provider and having this set in the default templates we're shipping? |
Maybe we can make AppVeyor uploads work again? |
Yes, we should/could do that |
Travis CI: Default to print to job log
AppVeyor: Capable of hosting artifacts
The text was updated successfully, but these errors were encountered: