all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Patchwork + automated checking and testing of patches
Date: Mon, 03 Dec 2018 00:51:36 +0000	[thread overview]
Message-ID: <87tvjvo2jr.fsf@cbaines.net> (raw)
In-Reply-To: <87tvjvzgwu.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1939 bytes --]


Chris Marusich <cmmarusich@gmail.com> writes:

> Hi Chris,
>
> This is really cool stuff!  Thanks for looking into it.
>
> Christopher Baines <mail@cbaines.net> writes:
>
>> I don't intend to do anything with Jenkins, as I think that wouldn't be
>> maintainable, but I think setting up some system to check some of the
>> following would be beneficial:
>
> I'm actually a little hesitant to ask, since I don't have time to
> contribute to this right now, and I don't want to bike-shed.  However,
> I'm just curious: why do you think using Jenkins wouldn't be
> maintainable?  I've read about Jenkins but haven't used it personally,
> and I've heard good things about it, so I'm curious to know why you
> prefer to avoid it entirely.

Sure, I've used Jenkins in different contexts, and indeed currently use
Jenkins, so I've got some experience here.

I'm obviously ignoring all the good parts here, but one source of data
is Debian. It used to have a package for Jenkins, and you can see some
of the work/issues here [1] and the thread about it's removal here [2].

One issue in particular to call out is some potential bootstrapping
issues [3] that seem to have been encountered.

It seems sensible to me to use Guix when doing things related to the
Guix project, like automated testing of patches (dogfooding, if you know
the term). Some of the things I've mentioned here lead me to doubt that
Jenkins will at some point be available through Guix.

So that's something about the maintainability of a Guix package, but
there's an operational component to this as well. The attack surface it
offers is maybe larger than sometimes necessary, if you only need a
read-only web interface for example.

1:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;dist=unstable;ordering=normal;repeatmerged=0;src=jenkins
2: https://lists.debian.org/debian-java/2016/01/msg00019.html
3: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714596

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]

  reply	other threads:[~2018-12-03  0:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31 10:43 Patchwork + automated checking and testing of patches Christopher Baines
2018-10-31 13:34 ` Tobias Geerinckx-Rice
2018-10-31 13:53   ` Christopher Baines
2018-11-01 15:22 ` Ludovic Courtès
2018-11-01 18:55   ` Christopher Baines
2018-11-06 13:26     ` Ludovic Courtès
2018-11-06 15:13       ` Gábor Boskovits
2018-11-06 18:52         ` Ricardo Wurmus
2018-11-07 18:40       ` Christopher Baines
2018-11-07 22:00         ` Ludovic Courtès
2018-11-19 19:32 ` Christopher Baines
2018-11-22  9:07   ` Ludovic Courtès
2018-12-02 22:45 ` Chris Marusich
2018-12-03  0:51   ` Christopher Baines [this message]
2018-12-08 21:27     ` Chris Marusich
2019-02-01 12:53 ` Christopher Baines
2019-02-04 21:20   ` Ludovic Courtès
2019-02-08 12:04     ` Christopher Baines
2019-02-08 18:54       ` Björn Höfling

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

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

  git send-email \
    --in-reply-to=87tvjvo2jr.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=cmmarusich@gmail.com \
    --cc=guix-devel@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.