From: "Clément Lassieur" <clement@lassieur.org>
To: "Gábor Boskovits" <boskovits@gmail.com>,
"Ricardo Wurmus" <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>,
Tatiana Sholokhova <tanja201396@gmail.com>
Subject: Re: Web interface pushed
Date: Fri, 10 Aug 2018 11:10:42 +0200 [thread overview]
Message-ID: <87600i1t9p.fsf@lassieur.org> (raw)
In-Reply-To: <CAE4v=phUYBxzD5FA2Y4ief1AfP=cFNG3pRfEUJhV4AcnMKkJEQ@mail.gmail.com>
Hello!
Gábor Boskovits <boskovits@gmail.com> writes:
>> > I have reconsidered the idea of having a
>> > separate page with build information, as I do not see what additional
>> > information we can display on this page except the link to the log file.
>> > So, for now I have added a link to the log file in the newly added column
>> > of the table with information about builds of an evaluation. What do you
>> > think about this?
>>
>> I think that’s fine for now.
>>
>> I’d like to show more information in the future, such as build time, git
>> change that triggered the build, links to packages that depend on this
>> build (and packages that affect this build in case of a propagated
>> failure), etc.
Note that there is no notion of 'package' in Cuirass. Most of the
things you said would work with 'derivations' though. But to add a link
to the package, we would need a way to find out if a derivation refers
to a package. I don't know how to do this.
> Here we could also find a place for things like previous builds, last
> successful build, last failing build later.
The 'job name' page I was talking about[1] is what you want, isn't it?
Clément
[1]: https://lists.gnu.org/archive/html/guix-devel/2018-08/msg00039.html
next prev parent reply other threads:[~2018-08-10 9:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-29 22:08 Web interface pushed Clément Lassieur
2018-07-29 23:46 ` Ludovic Courtès
2018-07-30 12:45 ` Pjotr Prins
2018-07-30 13:26 ` Ricardo Wurmus
2018-08-01 19:47 ` Tatiana Sholokhova
2018-08-02 6:53 ` Clément Lassieur
2018-08-02 16:00 ` Gábor Boskovits
2018-08-02 16:49 ` Clément Lassieur
2018-08-02 18:48 ` Gábor Boskovits
2018-08-02 19:21 ` Amirouche Boubekki
2018-08-02 20:16 ` Clément Lassieur
2018-08-02 18:13 ` Amirouche Boubekki
2018-08-02 20:17 ` Clément Lassieur
2018-08-03 13:53 ` Ricardo Wurmus
2018-08-04 21:53 ` Tatiana Sholokhova
2018-08-04 22:03 ` Ricardo Wurmus
2018-08-07 21:33 ` Tatiana Sholokhova
2018-08-09 9:17 ` Clément Lassieur
2018-08-09 19:59 ` amirouche
2018-08-09 20:46 ` Ricardo Wurmus
2018-08-10 5:01 ` Gábor Boskovits
2018-08-10 9:10 ` Clément Lassieur [this message]
2018-08-11 16:38 ` Ricardo Wurmus
2018-07-30 7:38 ` amirouche
2018-07-30 9:11 ` Clément Lassieur
2018-07-30 9:23 ` Alex Sassmannshausen
2018-07-30 9:41 ` Nils Gillmann
2018-07-30 12:08 ` Ricardo Wurmus
2018-07-30 12:14 ` Gábor Boskovits
2018-07-30 14:10 ` Hartmut Goebel
2018-07-30 16:02 ` Clément Lassieur
2018-07-30 18:43 ` Amirouche Boubekki
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=87600i1t9p.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
--cc=tanja201396@gmail.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://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).