On Fri, Feb 08, 2019 at 01:58:52AM +0100, SZEDER Gábor wrote: > On Thu, Feb 07, 2019 at 03:45:02PM -0500, Jeff King wrote: > > Fair enough. As an alternative, do you know offhand if there's an easy > > machine-readable way to get the CI results? If I could poll it with curl > > and generate my own notifications, that would be fine for me. > > Well, what do you mean by "CI results"? Getting whether a build > succeeded, failed, still running, etc.? Sure. Getting which > particular test script (semantic patch, documentation...) caused the > build failure? Nope. [1] Ideally yeah, I'd like to see the verbose (even "-x") log of the failed test. But even an indication of a failure is enough that I know I can start digging (and bonus if I can then dig into the log with a script and parse it myself). > Travis CI has a REST API (note that you have to sign in with GitHub > account to view its docs, and then need an access token to use the > API): Thanks, I may poke around that. In this particular case, though, I was wondering about the Azure Pipelines builds that Dscho has put together. > Depending on what you want that in itself might already be enough for > you. It wasn't for me, as I have a very particular idea about how I > prefer to view my CI results, but neither the website nor the CLI > client offer such a compact _and_ detailed view like this: > > ccccccccc 2175 pu > ccccccccc 2174 sg/ci-parallel-build > ccccccccc 2173 js/fuzz-commit-graph-update > ccccccccc 2172 js/mingw-host-cpu > PsscsPscc 2171 dl/submodule-set-branch > PPXsPPPPP 2170 kl/pretty-doc-markup-fix > PPPPPPPPP 2169 en/combined-all-paths Mostly I just want to see the status of my own topics (ideally as soon as they're available, but even polling to get them within a few hours would be OK). I run the tests locally, of course, but sometimes problems show up on other platforms. -Peff
