unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: Multi-OS Emacs buildbot?
Date: Sun, 20 Dec 2020 18:40:45 +0100	[thread overview]
Message-ID: <87lfdscr4y.fsf@gnus.org> (raw)
In-Reply-To: <ca6ae3c9-bb5b-16d8-5d17-7da4a8fdf125@yandex.ru> (Dmitry Gutov's message of "Sun, 20 Dec 2020 15:58:16 +0200")

Dmitry Gutov <dgutov@yandex.ru> writes:

>> And remember, Dick promised
>> to set up a real multi-platform CI thing at some buildbot service or
>> other, and we won't need this super-simple one then.
>
> In case you're not being snarky here:
>
> There are free-ish CI solutions which we could use, one example is
> CircleCI (https://circleci.com/open-source/).

I am totally being snarky, because (in my experience) setting up CI for
a project takes a bit of work to get to a useful state, especially when
doing CI over a wide range of systems.  If somebody is willing to do the
work, that'd be wonderful, but apparently nobody is?

So instead we have the current state, where hydra builds on Debian, and
that's it.  (Plus Emba, and I don't know what systems it's building on,
really.)

> So to use it we would have to rely on a GitHub mirror. Can/should we
> do that?
>
> There is one at https://github.com/emacs-mirror/emacs/, but we don't
> know who controls it, so we can't ask them to set up the integration
> from that side.

I think anybody's that interested can set this up in whatever way
they want to.  The CI doesn't have to be a GNU/FSF-approved thing.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2020-12-20 17:40 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-19 15:58 Multi-OS Emacs buildbot? Lars Ingebrigtsen
2020-12-19 16:27 ` dick.r.chiang
2020-12-19 17:49   ` Lars Ingebrigtsen
2020-12-19 18:43 ` Pankaj Jangid
2020-12-19 18:48   ` Lars Ingebrigtsen
2020-12-19 18:57     ` Yuri Khan
2020-12-19 19:01     ` Pankaj Jangid
2020-12-19 19:02       ` Lars Ingebrigtsen
2020-12-19 19:04         ` Lars Ingebrigtsen
2020-12-19 19:15           ` Pankaj Jangid
2020-12-19 19:18             ` Lars Ingebrigtsen
2020-12-20  2:35               ` Pankaj Jangid
2020-12-20  4:17                 ` Thien-Thi Nguyen
2020-12-20  5:16                   ` Pankaj Jangid
2020-12-20  6:54                 ` Tim Landscheidt
2020-12-20  8:17                   ` Pankaj Jangid
2020-12-20  8:56                     ` Thien-Thi Nguyen
2020-12-20 10:10                       ` Pankaj Jangid
2020-12-20 20:44                     ` Tim Landscheidt
2020-12-21  3:36                       ` Pankaj Jangid
2020-12-21  3:40                         ` Lars Ingebrigtsen
2020-12-21  5:58                           ` Pankaj Jangid
2020-12-20 13:58               ` Dmitry Gutov
2020-12-20 17:40                 ` Lars Ingebrigtsen [this message]
2020-12-20 18:03                   ` Dmitry Gutov
2020-12-20 18:08                     ` Lars Ingebrigtsen
2020-12-20 18:30                       ` Dmitry Gutov
2020-12-22  6:27                         ` Lars Ingebrigtsen
2020-12-22 12:01                           ` Dmitry Gutov
2020-12-19 19:27           ` Mising posts in thread from gwene Was: " Pankaj Jangid
2020-12-19 19:42             ` Lars Ingebrigtsen
2020-12-20  2:40               ` Pankaj Jangid
2020-12-19 19:10 ` Lars Ingebrigtsen
2020-12-19 21:45   ` 'make check' errors on Debian (was: Multi-OS Emacs buildbot?) Basil L. Contovounesios
2020-12-19 21:48     ` 'make check' errors on Debian Lars Ingebrigtsen
2020-12-20  6:39   ` Multi-OS Emacs buildbot? Richard Stallman
2020-12-20 17:30     ` Lars Ingebrigtsen
2020-12-19 20:16 ` Alan Third
2020-12-19 21:11   ` Lars Ingebrigtsen
2020-12-20  8:50     ` Michael Albinus
2020-12-20 14:04       ` Dmitry Gutov
2020-12-20 14:11         ` Michael Albinus
2020-12-20 17:32           ` Dmitry Gutov
2020-12-22  6:23             ` Toon Claes
2020-12-22 17:32               ` Michael Albinus
2020-12-23  7:11                 ` Lars Ingebrigtsen
2020-12-23  8:13                   ` Michael Albinus
2020-12-25 17:19                 ` Toon Claes
2020-12-25 17:34                   ` Michael Albinus
2020-12-25 19:40                   ` Lars Ingebrigtsen
2020-12-25 20:17                     ` Michael Albinus
2020-12-25 20:22                       ` Lars Ingebrigtsen
2020-12-25 20:38                         ` Michael Albinus
2020-12-25 20:43                           ` Lars Ingebrigtsen
2020-12-26  8:56                             ` Michael Albinus
2020-12-27  9:03                               ` Toon Claes
2020-12-27 10:01                                 ` Michael Albinus
2020-12-30 13:43                                   ` Toon Claes
2020-12-30 15:28                                     ` Alan Third
2020-12-31 14:14                                     ` Michael Albinus
2020-12-20 17:35       ` Lars Ingebrigtsen
2020-12-20 18:11         ` Michael Albinus
2020-12-22  6:28           ` Lars Ingebrigtsen
2020-12-19 20:20 ` Michael Albinus
2020-12-19 20:46 ` Daniel Martín
2020-12-19 21:12   ` Lars Ingebrigtsen
2020-12-22 15:37 ` Nikolay Kudryavtsev
2020-12-23  7:10   ` Lars Ingebrigtsen
2020-12-23 15:37     ` Eli Zaretskii

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87lfdscr4y.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=dgutov@yandex.ru \
    --cc=emacs-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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).