From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: bug#32575: [Cuirass] Filter results by architecture Date: Thu, 30 Aug 2018 10:09:17 +0200 Message-ID: <87r2ig9sya.fsf@elephly.net> References: <87a7p5b7x3.fsf@elephly.net> <877ek8dhkm.fsf@fastmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48925) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fvpXW-0002Mi-0r for bug-guix@gnu.org; Fri, 31 Aug 2018 15:57:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fvpXS-0006zr-S3 for bug-guix@gnu.org; Fri, 31 Aug 2018 15:57:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:36052) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fvpXS-0006zi-LJ for bug-guix@gnu.org; Fri, 31 Aug 2018 15:57:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fvpXS-0006uY-Eh for bug-guix@gnu.org; Fri, 31 Aug 2018 15:57:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <877ek8dhkm.fsf@fastmail.com> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Joshua Branson Cc: 32575@debbugs.gnu.org Hi Joshua, > Ricardo Wurmus writes: > >> The Cuirass web interface shows the number of successful, failed, and >> pending builds for each evaluation. Looking at just these numbers it is >> impossible to tell, how each of the supported architectures is affected. >> >> It would be good if we could separate the view by architecture. Then we >> could more easily determine that a change broke many builds for one >> architecture while fixing builds on another. >> >> One way to do this would be to accept an optional query variable, e.g. >> >> http://ci.guix.info/jobset/guix-master?system=3Dx86_64-linux > > That is an option. Another one is using a REST API. It seems to have > all the hype these days. So the URL would turn into: > > http://ci.guix.info/jobset/guix-master/system/x86_64-linux > > Though I freely admit, I don't completely understand the benefits of REST. REST doesn=E2=80=99t quite apply here, because we only use GET =E2=80=94 th= e Cuirass web interface is read-only. A big part of REST is to use HTTP verbs in an appropriate manner and keep the URLs as resource identifiers the same for all verbs. What you refer to is the related trend to using Clean URLs: https://en.wikipedia.org/wiki/Clean_URL These are often used with a RESTful API. I think that filtering of a dynamic resource could very well be done with a GET query string. A Clean URL would make more sense for something that doesn=E2=80=99t change as quickly (e.g. a particular product= in a catalogue). -- Ricardo