Re: using Cuirass to track a guix packages' git

[Jan Nieuwenhuizen]

Mathieu Lirzin writes:

> Intuitively I would prefer "#:compile?" but both are OK, so we can stick
> with "#:no-compile?" if that's more convenient.

Yes, me too.  Let's see where this goes, it can prolly be changed easily
later.

>>> Can you send the updated patches?
>>
>> Sure, find attached.
>
> Pushed with minor cosmetic changes.  :)

Nice changes.  Thanks.

> Given the current state of Cuirass, I think it is OK to not provide
> documentation while experimenting.

Ok.

>> Thanks!  I'd really love to get a working Guix-based ci system and
>> Cuirass is already very close to the minimal set that I need.  I have
>> a working patch to add building of VMs (a la hydra/guix-system.scm) but
>> it needs a bit of cleanup work.
>
> Nice!

I figure we experiment and maintain this in Cuirass and move into Guix
again later.

> There is a basic Guile Web server which is runnable via
> 'run-cuirass-server' procedure.  There is only one JSON ressource which
> is accessible from "/specifications" and "/jobsets" routes.  To use the
> server you have to parameterize the '%package-database' parameter to
> point to an SQLite file with specifications in it.

Yes, I think I found this, I can see json in my browser window...but
that's not really a web view yet (no criticism, I'm just wondering...)

> What needs to be done is to provide more JSON ressources (inspired by
> Hydra API) by translating request to SQL queries.  A command line
> interface would be a nice addition too.

If this is inspired by Hydra does it mean you plan to somehow use (parts
of?) the Hydra web engine to present views using this json?

Greetings,
Jan.

-- 
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar®  http://AvatarAcademy.nl