unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Brinkhoff <lars@nocrew.org>
Cc: emacs-devel@gnu.org
Subject: Re: GitLab CI setup file in scratch/tzz/gitlab
Date: Thu, 27 Apr 2017 17:23:54 +0300	[thread overview]
Message-ID: <83efwend39.fsf@gnu.org> (raw)
In-Reply-To: <864lxal9zf.fsf@molnjunk.nocrew.org> (message from Lars Brinkhoff on Thu, 27 Apr 2017 07:01:40 +0200)

> From: Lars Brinkhoff <lars@nocrew.org>
> Date: Thu, 27 Apr 2017 07:01:40 +0200
> 
> Eli Zaretskii wrote:
> >> Ted Zlatanov wrote:
> >> I've pushed a .gitlab-ci.yml file to the branch scratch/tzz/gitlab
> >> John, Eli, any objections?
> >
> > Frankly, I don't understand why this file should be part of the Emacs
> > repository.  For starters, it seems to be Debian-specific.  And if it
> > should be in our repository, its place is definitely wrong, it should
> > be somewhere under admin/.
> 
> It's not Debian-specific.  It does mention "debian", but that's only to
> pick one out of many possible images to run the build.

I actually meant the 'apt' commands.  It's true that some other
distributions besides Debian support that, but AFAIK they have their
own commands to the same effects.

> It's probably required to be in the top-level directory to work with
> GitLab-CI.  I haven't checked GitLab specifically, but most continuous
> integration services does have this requirement that the configuration
> file must have a specific name, and must be in the root of the project.
> 
> With this file in place, GitLab can now run a full build and test
> cycle for every commit:
> 
> https://gitlab.com/emacs-ci/emacs/builds/14381164

OK, but why should the Emacs repository keep this file and maintain
it?  It looks simple enough for the interested users to have it on
their systems, and GitLab looks like a full repository anyway, so
maybe the file should be maintained there?  Or we could have a small
note file in admin/notes telling the interested users to create such a
file if they want.

IOW, this file looks unrelated to Emacs, so I don't think I understand
why Ted wanted us to maintain it.  I'm probably missing something.



  reply	other threads:[~2017-04-27 14:23 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26 18:45 GitLab CI setup file in scratch/tzz/gitlab Ted Zlatanov
2017-04-26 18:51 ` Eli Zaretskii
2017-04-26 20:55   ` dptd dptd
2017-04-27  5:01   ` Lars Brinkhoff
2017-04-27 14:23     ` Eli Zaretskii [this message]
2017-04-27 14:37       ` Dmitry Gutov
2017-04-27 14:59         ` Eli Zaretskii
2017-04-27 15:16           ` Dmitry Gutov
2017-04-28 21:33             ` Richard Stallman
2017-04-29  0:41               ` Ted Zlatanov
2017-04-29 15:58                 ` Richard Stallman
2017-04-29 17:44                   ` Dmitry Gutov
2017-04-30 22:19                     ` Richard Stallman
2017-04-30 23:55                       ` Dmitry Gutov
2017-05-01  1:53                         ` Ted Zlatanov
2017-05-01 15:54                         ` Richard Stallman
2017-05-02 12:42                           ` Richard Stallman
2017-05-03  0:06                           ` Dmitry Gutov
2017-05-03 19:15                             ` Richard Stallman
2017-05-14  2:25                               ` Ted Zlatanov
2017-05-15  1:44                                 ` Richard Stallman
2017-05-15 20:08                                   ` Ted Zlatanov
2017-05-18  1:12                                   ` Perry E. Metzger
2017-05-19  1:19                                     ` Richard Stallman
2017-05-19  1:53                                       ` Perry E. Metzger
2017-05-21  3:25                                         ` Richard Stallman
2017-05-21  3:49                                           ` Jean-Christophe Helary
2017-05-22 12:15                                             ` Richard Stallman
2017-05-21 15:19                                   ` Tino Calancha
2017-04-29 18:22                 ` Lars Brinkhoff
2017-04-29 21:11                   ` Ted Zlatanov
2017-04-30 22:20                   ` Richard Stallman
2017-04-29  1:29               ` Mike Gerwitz
2017-04-27 17:43       ` Lars Brinkhoff
2017-04-27 20:16         ` Dmitry Gutov
2017-04-27 20:42           ` Eli Zaretskii
2017-04-27 23:20             ` Dmitry Gutov
2017-04-28  6:49               ` Eli Zaretskii
2017-04-28  8:33                 ` Dmitry Gutov
2017-04-28  9:45                   ` Eli Zaretskii
2017-04-28  9:58                     ` Dmitry Gutov
2017-04-28 13:17                       ` Eli Zaretskii
2017-04-28 13:35                         ` Dmitry Gutov
2017-04-28 12:47                     ` Ted Zlatanov
2017-04-28 13:24                       ` Lars Brinkhoff
2017-04-28 14:16                         ` Ted Zlatanov
2017-04-27 20:27         ` Eli Zaretskii
2017-04-28 21:34       ` Richard Stallman
2017-04-27 16:16   ` Ted Zlatanov
2018-07-23 13:14     ` Tino Calancha
2018-07-27 13:48       ` Toon Claes

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=83efwend39.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lars@nocrew.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).