From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Jeff King <peff@peff.net>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Martin Ågren" <martin.agren@gmail.com>,
git@vger.kernel.org, "Eric Sunshine" <sunshine@sunshineco.com>
Subject: Re: [PATCH v3] doc-diff: don't `cd_to_toplevel`
Date: Fri, 8 Feb 2019 01:58:52 +0100 [thread overview]
Message-ID: <20190208005852.GT10587@szeder.dev> (raw)
In-Reply-To: <20190207204502.GA28893@sigill.intra.peff.net>
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]
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):
https://developer.travis-ci.org/gettingstarted
They also offer a command line client for this API:
https://github.com/travis-ci/travis.rb
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
('c' - created, 's' - started, 'P' - passed, 'X' - failed)
Nothing that can't be achived with good screenful of Python/Ruby/etc
scripting... including colors matching the website's color scheme! :)
[1] Although since we include the trash directory of the failed test
script in the logs, surrounded by clear marker lines containing
the failed test script's name, it wouldn't be too hard to get it
programmatically, either.
next prev parent reply other threads:[~2019-02-08 0:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-03 8:35 [PATCH] doc-diff: don't `cd_to_toplevel` before calling `usage` Martin Ågren
2019-02-03 9:08 ` Eric Sunshine
2019-02-03 9:11 ` Eric Sunshine
2019-02-03 10:35 ` Martin Ågren
2019-02-03 11:01 ` Eric Sunshine
2019-02-03 11:08 ` [PATCH v2] " Martin Ågren
2019-02-03 23:01 ` Jeff King
2019-02-04 20:50 ` [PATCH v3] doc-diff: don't `cd_to_toplevel` Martin Ågren
2019-02-04 23:34 ` Jeff King
2019-02-05 10:34 ` Johannes Schindelin
2019-02-05 18:45 ` Junio C Hamano
2019-02-06 12:20 ` Johannes Schindelin
2019-02-06 17:24 ` Junio C Hamano
2019-02-06 18:55 ` Jeff King
2019-02-07 15:41 ` Johannes Schindelin
2019-02-07 17:37 ` Junio C Hamano
2019-02-07 21:34 ` Johannes Schindelin
2019-02-07 20:49 ` Jeff King
2019-02-07 21:42 ` Johannes Schindelin
2019-02-06 18:49 ` Jeff King
2019-02-07 14:26 ` Johannes Schindelin
2019-02-07 20:45 ` Jeff King
2019-02-07 21:57 ` Johannes Schindelin
2019-02-08 2:53 ` Jeff King
2019-02-08 4:34 ` Jeff King
2019-02-08 0:58 ` SZEDER Gábor [this message]
2019-02-08 2:51 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190208005852.GT10587@szeder.dev \
--to=szeder.dev@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=martin.agren@gmail.com \
--cc=peff@peff.net \
--cc=sunshine@sunshineco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).