unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Multi-OS Emacs buildbot?
Date: Sat, 19 Dec 2020 21:20:40 +0100	[thread overview]
Message-ID: <87tush35uv.fsf@gmx.de> (raw)
In-Reply-To: <871rfliy8h.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 19 Dec 2020 16:58:38 +0100")

Lars Ingebrigtsen <larsi@gnus.org> writes:

Hi Lars,

> Over the past few months, I've installed a whole bunch of VMs with
> different operating systems to help debug various problems.  Now that
> I've got them, I'm wondering whether it would be helpful to do a
> buildbot kind of thing across them all?
>
> This can either be a lot of work if done right, or it can be done very
> simply.  Doing it right would mean automatically building on all
> commits, and notifying the committer about breakages etc...  but that's,
> like, real work, and I'm not volunteering to do that at all.
>
> A much simpler solution would be to just write a script that ssh-es to
> all the VMs once a day, "git pull; make bootstrap; make check" and then
> make a summary report on all the tests that fail to some new Emacs
> mailing list.  I can do that; it's trivial.
>
> It'd be...  somewhat useful?  But not really that useful?  Opinions?
>
> (My current VM collection is FreeBSD, NetBSD, OpenBSD, Windows 10
> w/Cygwin, Macos-es catalina, mojave and high sierra (with HomeBrew),
> Macos catalina (with Macports), and Fedora.  Big Sur and Windows 10
> w/MinGW soon to follow.)

We have the CI infrastructure on emba.gnu.org. Looks like your VMs are
perfect candidates for GitLab runners from that.

<https://emba.gnu.org/emacs/emacs/pipelines>

<https://docs.gitlab.com/runner/>

Best regards, Michael.



  parent reply	other threads:[~2020-12-19 20:20 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
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 [this message]
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=87tush35uv.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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).