From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jeff King <peff@peff.net>
Cc: "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: Thu, 7 Feb 2019 22:57:48 +0100 (STD) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1902072245020.41@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <20190207204502.GA28893@sigill.intra.peff.net>
Hi Peff,
On Thu, 7 Feb 2019, Jeff King wrote:
> On Thu, Feb 07, 2019 at 03:26:21PM +0100, Johannes Schindelin wrote:
>
> > > So IMHO this isn't really a show-stopper problem, so much as
> > > something that is a sign of the maturing test/CI setup (I say
> > > "maturing", not "mature", as it seems we've probably still got a
> > > ways to go). As far as notifications go, it probably makes sense for
> > > them to be something that requires the user to sign up for anyway,
> > > so at that point they're making their own choice about whether the
> > > signal to noise ratio is acceptable.
> >
> > Maybe. I do not even know whether there is an option for that in Azure
> > Pipelines, maybe GitHub offers that?
>
> No, I don't think so. Probably the route there would be to make a
> comment on the commit or PR that would then go to the user as a
> notification (from which they can then decide on email delivery, etc).
Ah, but that won't notify you when a Check failed. So that still would
require some scripting.
> > In any case, I just wanted to corroborate with a real-world example
> > what I mentioned at the Contributors' Summit: that I would like to not
> > script that thing yet where contributors are automatically notified
> > when their branches don't pass.
>
> 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.
There is a REST API:
https://docs.microsoft.com/en-us/rest/api/azure/devops/build/builds/list?view=azure-devops-rest-5.0
So this would give you the latest 5 failed builds:
curl "https://dev.azure.com/gitgitgadget/git/_apis/build/builds?definitions=6&resultFilter=failed&\$top=5"
I did not find a way to filter by user, or by branch name with wildcards,
though.
> > Speaking of which... can we hook it up with https://github.com/git/git,
> > now that the Azure Pipelines support is in `master`? I sent you and Junio
> > an invitation to https://dev.azure.com/git/git, so that either you or
> > Junio (who are the only owners of the GitHub repository) can set it up. If
> > you want me to help, please do not hesitate to ping me on IRC.
>
> I'm happy to. I walked through the Azure setup/login procedure, but I'm
> not sure what to do next.
The next step would be to install Azure Pipelines from the Marketplace and
activate it for git/git. There *should* be a wizard or something to walk
you through...
Ciao,
Dscho
next prev parent reply other threads:[~2019-02-07 21:57 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 [this message]
2019-02-08 2:53 ` Jeff King
2019-02-08 4:34 ` Jeff King
2019-02-08 0:58 ` SZEDER Gábor
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=nycvar.QRO.7.76.6.1902072245020.41@tvgsbejvaqbjf.bet \
--to=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).