unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Roel Janssen <roel@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Adding build status to the package list table
Date: Wed, 25 Nov 2015 14:56:56 +0100	[thread overview]
Message-ID: <87oaeifahj.fsf@gnu.org> (raw)
In-Reply-To: <87fuzvo7i3.fsf@gnu.org> (Roel Janssen's message of "Tue, 24 Nov 2015 14:24:20 +0100")

Roel Janssen <roel@gnu.org> skribis:

> I've attached a patch that adds status icons to the links in the
> expanded view. It only loads when the user clicks on "expand".

This is great!

Minor things: I would move the patch list above the status, and remove
the “status:” heading.

> We might need to add a HTTP header from the GNU server to allow
> loading data from external sources:
>
>   https://en.wikipedia.org/wiki/Cross-origin_resource_sharing

Indeed, because here the requests get blocked.  Could you get in touch
with webmasters@gnu.org and report back?

> I hope my commit message is OK this way.

It’s almost perfect.  ;-)  The only missing bits are the changes to
packages.css that are not mentioned, and the added files that must be
listed.

> For fetching all statuses in one API call, I would like to propose
> adding a function to Hydra that can return the status in an array like
> the following JSON code:
>
> [
>   {"timestamp":1447890755,"buildstatus":0,"job":"a2ps-4.14.x86_64-linux","jobset":"master","project":"gnu","system":"x86_64-linux","nixname":"a2ps-4.14","finished":1,"id":812555},
>   {"finished":1,"id":811961,"system":"i686-linux","nixname":"a2ps-4.14","project":"gnu","jobset":"master","job":"a2ps-4.14.i686-linux","timestamp":1447890647,"buildstatus":0},
>   {"timestamp":1447890485,"buildstatus":0,"job":"a2ps-4.14.armhf-linux","nixname":"a2ps-4.14","system":"armhf-linux","id":811309,"finished":1,"jobset":"master","project":"gnu"},
>   ...
> ]
>
> Then I could add columns to the table with build status icons. I don't
> know the Hydra code (or Perl), so I wonder if anyone else has the time
> and wants to add the API call.

I’d rather avoid hacking it, to be honest ;-), but I don’t mind if
someone else does, of course.

Thank you!

Ludo’.

  reply	other threads:[~2015-11-25 13:57 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19 12:50 Adding build status to the package list table Roel Janssen
2015-11-19 19:57 ` Mark H Weaver
2015-11-19 21:25   ` Eric Bavier
2015-11-19 22:47     ` Roel Janssen
2015-11-20 16:31       ` Mark H Weaver
2015-11-21 15:21         ` Roel Janssen
2015-11-20 14:18 ` Ludovic Courtès
2015-11-20 16:43   ` Roel Janssen
2015-11-20 21:46     ` Pjotr Prins
2015-11-20 22:49     ` Ludovic Courtès
2015-11-21 15:24       ` Roel Janssen
2015-11-21 15:36         ` Pjotr Prins
2015-11-21 15:59         ` Ludovic Courtès
2015-11-24 13:24           ` Roel Janssen
2015-11-25 13:56             ` Ludovic Courtès [this message]
2015-11-27  0:16               ` Roel Janssen
2016-01-04 20:12               ` Roel Janssen
2016-01-06 16:03                 ` Ludovic Courtès
2016-01-06 16:55                   ` Roel Janssen
2016-01-06 22:20                     ` Ludovic Courtès
2016-02-01 23:23                       ` Roel Janssen
2016-02-03  9:28                         ` Ludovic Courtès
2016-02-03  9:41                           ` Ricardo Wurmus
2016-02-03 10:32                             ` Roel Janssen
2016-01-21 10:11                     ` Ludovic Courtès
2016-01-21 23:29                       ` Roel Janssen
2016-01-22  8:54                         ` Ludovic Courtès

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: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87oaeifahj.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=roel@gnu.org \
    /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://git.savannah.gnu.org/cgit/guix.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).