From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Lars Brinkhoff Newsgroups: gmane.emacs.devel Subject: Re: GitLab CI setup file in scratch/tzz/gitlab Date: Thu, 27 Apr 2017 19:43:36 +0200 Organization: nocrew Message-ID: <86h919kapj.fsf@molnjunk.nocrew.org> References: <87shkvnh2z.fsf@lifelogs.com> <83inlrngte.fsf@gnu.org> <864lxal9zf.fsf@molnjunk.nocrew.org> <83efwend39.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1493315035 15202 195.159.176.226 (27 Apr 2017 17:43:55 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 27 Apr 2017 17:43:55 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Apr 27 19:43:52 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d3nSI-0003px-F3 for ged-emacs-devel@m.gmane.org; Thu, 27 Apr 2017 19:43:50 +0200 Original-Received: from localhost ([::1]:33497 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d3nSO-0006On-1x for ged-emacs-devel@m.gmane.org; Thu, 27 Apr 2017 13:43:56 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39593) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d3nSG-0006OW-IB for emacs-devel@gnu.org; Thu, 27 Apr 2017 13:43:49 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d3nSD-0007u5-EO for emacs-devel@gnu.org; Thu, 27 Apr 2017 13:43:48 -0400 Original-Received: from [195.159.176.226] (port=43202 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d3nSD-0007tm-7a for emacs-devel@gnu.org; Thu, 27 Apr 2017 13:43:45 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1d3nS4-0003Y1-9c for emacs-devel@gnu.org; Thu, 27 Apr 2017 19:43:36 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 43 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:LWnusWvUFiNXcQf99xG9tCKBkMY= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:214359 Archived-At: Eli Zaretskii wrote: > 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. Right, the build runs in a Debian image, so it must use Debian package management commands. Whatever operating system you pick, you must provide some instructions to install build dependencies. > We didn't yet decide that this site will be our CI site. Until we do, > why should we function as someone else's repository?? I think it would be reasonable to take that decision first, and add the file second. It has been demonstrated to work. Now it has to be cleared by Emacs maintainers, FSF policies, etc. > 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 It would be possible, but no that simple. There would to be a commit (or patch) with the .gitlab-ci.yml file which would have to be rebased on top of master (or any oher branch to be tested) every time the GitLab repository is synchronized with savannah. Yes, this could be done. But it seems to me that this would be brittle and prone to failures. Someone would have to look after this. If the file could just sit in the savannah repository, it would be more likely to be useful. > 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. I have experimented with about a dozen different CI services, and to me it seems quite reasonable that Emacs should have this file, IF the maintainers decide that GitLab-CI is to be used for continuous integration. It's not unrelated to Emacs. It provides build and testing instructions to an automated service. Those instuctions are specific to Emacs.