... or the reason why I wish I could smash my keyboard with a 12-foot H-beam.
Accessibility wise, this shipable web interface thingy is a complete
abomination. Every of my attempts to get to test failure logs ended up
in a failure of its own. And recursive failure is not good.
Is there a way to bypass the web UI?
I found http://docs.shippable.com/ci/email-notifications/ which looked
promising. But that affects the entire project for everybody. All I want
is access to failure reports for my own commits without the dreaded web
Any help would be greatly appreciated!
On Jul 30, 2019, at 10:36 PM, Nicolas Pitre <email@example.com> wrote:No sure, but probably can ask on https://github.com/Shippable/support
On 31 Jul 2019, at 18:16, Kumar Gala <firstname.lastname@example.org> wrote:On Jul 30, 2019, at 10:36 PM, Nicolas Pitre <email@example.com> wrote:No sure, but probably can ask on https://github.com/Shippable/support
Shippable's "rich" UI affects not just accessibility but also
any user trying to perform simple things like searching for some
specific error message across all 5 shards or (let's go crazy) across
different runs. Don't even think about gathering data about sporadic
failures like for instance the ones described in
One important CI principle is "automate everything" but
Shippable web UI is not meant for that. Maybe there's a another,
lower level way to access CI logs and results?