On Wed, 19 Jun 2019 21:49:50 +0200
Ricardo Wurmus wrote:
> Danny Milosavljevic writes:
>
> > On Tue, 18 Jun 2019 19:50:25 +0200
> > Björn Höfling wrote:
> >
> >> * I would like to know that I'm on page k/n.
> >
> > That web interface is a frontend to a dynamically changing database
> > (an
On Fri, 21 Jun 2019 17:18:38 +0200
Ludovic Courtès wrote:
> Hello!
>
> I’d just like to say that we should think not just in terms of a web
> interface, but also in terms of an HTTP API + CLI/Emacs.
+1
Would you like to formulate out a bug with what you are missing?
> Things like ‘guix chall
Hello!
I’d just like to say that we should think not just in terms of a web
interface, but also in terms of an HTTP API + CLI/Emacs.
Things like ‘guix challenge’, ‘guix weather’, and build-farm.el are
pretty nice to me as a user, so I think we should keep an eye on how we
can make such tools poss
Danny Milosavljevic writes:
> On Tue, 18 Jun 2019 19:50:25 +0200
> Björn Höfling wrote:
>
>> * I would like to know that I'm on page k/n.
>
> That web interface is a frontend to a dynamically changing database
> (and a quickly changing database at that).
>
> What would "page" even mean there?
Hi Björn,
On Tue, 18 Jun 2019 19:50:25 +0200
Björn Höfling wrote:
> * I would like to know that I'm on page k/n.
That web interface is a frontend to a dynamically changing database
(and a quickly changing database at that).
What would "page" even mean there?
And the "/n" part is impossible to
Björn Höfling writes:
> * If a job failed because of its dependency, I would like to see which
> one caused the problem. I don't know how to find that out.
> In Hydra, the name and build log of the failing dependency was directly
> available.
This is now implemented on the “details” page. The
Björn Höfling writes:
> It's nice that there is a search now, but it's not enough for me :-)
>
> The search string disappears from the search box. It would be very nice
> if it would be kept, then I can remember and refine it if necessary.
This is now implemented.
--
Ricardo
On Wed, 19 Jun 2019 10:23:57 +0200
Ricardo Wurmus wrote:
> Ricardo Wurmus writes:
>
> > Hi Björn,
> >
> >> * I'm really missing the tabs/filters like in Hydra: "succeding",
> >> "newly succeding", "newly failing", ...
> >> In having all jobs in one big list is annoying. I care usually only
>
Ricardo Wurmus writes:
> Hi Björn,
>
>> * I'm really missing the tabs/filters like in Hydra: "succeding",
>> "newly succeding", "newly failing", ...
>> In having all jobs in one big list is annoying. I care usually only
>> about failures.
>
> Cuirass now has tabs, though it won’t show “newly” s
Hi Björn,
> * I'm really missing the tabs/filters like in Hydra: "succeding",
> "newly succeding", "newly failing", ...
> In having all jobs in one big list is annoying. I care usually only
> about failures.
Cuirass now has tabs, though it won’t show “newly” succeding or failing
jobs. It just
Björn Höfling writes:
> Homepage/Specifications list:
>
> * The list of specifications should be ordered alphabetically by its
> name.
Done.
--
Ricardo
Hi Björn,
> I would like to see a "build series" for a specific job/system
> combination.
>
> For that, In Hydra I searched for the job name. It first presented me
> with a list of
> "types", like "maven: master/i386" or "maven: staging/x86_64".
>
> Then I had to click one of them to see that sp
12 matches
Mail list logo
