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
