danger / Peril

Getting temp CI results

Getting temp CI results

March 14, 2018 · 2:57pm
The danger-plugin-jest works by having Jest output the results as a test-results.json file to the CI server, then fs.readFile -ing it, formatting it to markdown and posting it.
How would something like that work in Peril? For my use case, I'm trying to make danger-plugin-flow post the Flow errors/warnings in the PR comment. Flow has a --json option too and I'm sure I could make that work with Danger but how'd I make that work with Peril?

March 14, 2018 · 7:23pm

For Peril, it really might just _not_ be possible. You'd have to upload a build artifact somewhere for the separate file to be read.

like-fill
0

It's one of the big separations of concerns, but I also really like the messing aspect of reading the JSON file and pulling out some useful metadata. So far, we've just removed any rules that don't need this kind of access and move them to peril

like-fill
0

I see, I thought so

like-fill
0

Maybe that could be its own paid addon to Peril once you start hosting it for people?

like-fill
0

"Pay for a nice wrapper around S3 that'll automatically work with this this and that plugin"

like-fill
0

March 15, 2018 · 2:23pm

Aye, I agree

like-fill
0
Your message here...

**bold***italics*`code````preformatted```