CI-agnostic way to display logs on failure

ropensci / tic

Tasks Integrating Continuously: CI-Agnostic Workflow Definitions

https://docs.ropensci.org/tic

154 stars 18 forks source link

CI-agnostic way to display logs on failure #19

Open krlmlr opened 7 years ago

krlmlr commented 7 years ago

Travis CI: Default to print to job log AppVeyor: Capable of hosting artifacts

krlmlr commented 6 years ago

Push artifacts to an orphan branch, tag it, print link to console.

krlmlr commented 6 years ago

Can be achieved (mostly) with existing code, create a demo package to illustrate this.

step_rcmdcheck() needs to keep check output (optionally or only when failing)
setup SSH keys for the "after_failure" stage, use a branch name generated from ci()$get_build_number()

Orphan branches are problematic because they will be downloaded by default when the user does git fetch . But maybe that's not much of a problem if only logs for failed builds are pushed.

pat-s commented 4 years ago

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?

krlmlr commented 4 years ago

Maybe we can make AppVeyor uploads work again?

pat-s commented 4 years ago

Yes, we should/could do that