unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: GitLab CI setup file in scratch/tzz/gitlab
Date: Thu, 27 Apr 2017 12:16:30 -0400	[thread overview]
Message-ID: <87zif1n7vl.fsf@lifelogs.com> (raw)
In-Reply-To: 83inlrngte.fsf@gnu.org

On Wed, 26 Apr 2017 21:51:09 +0300 Eli Zaretskii <eliz@gnu.org> wrote: 

>> From: Ted Zlatanov <tzz@lifelogs.com>
>> Date: Wed, 26 Apr 2017 14:45:24 -0400
>> 
>> I've pushed a .gitlab-ci.yml file to the branch scratch/tzz/gitlab
>> 
>> Merging that branch and letting me and Toon maintain that file would
>> make it much easier to support https://gitlab.com/emacs-ci/emacs and
>> further evaluate its viability as a CI service.

EZ> Frankly, I don't understand why this file should be part of the Emacs
EZ> repository.  For starters, it seems to be Debian-specific.  And if it
EZ> should be in our repository, its place is definitely wrong, it should
EZ> be somewhere under admin/.

The contents and location are annoyingly necessary in order to try out
Gitlab as a CI service.

On Thu, 27 Apr 2017 17:23:54 +0300 Eli Zaretskii <eliz@gnu.org> wrote: 

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

Because it's a pain otherwise. If we use Gitlab CI more fully, we have
to keep it there. They are working on allowing the location to be
flexible: https://gitlab.com/gitlab-org/gitlab-ce/issues/15041
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5682 so this is
probably not a long-term problem.

On Thu, 27 Apr 2017 17:59:30 +0300 Eli Zaretskii <eliz@gnu.org> wrote: 

EZ> I don't understand this attack.  We didn't yet decide that this site
EZ> will be our CI site.  Until we do, why should we function as someone
EZ> else's repository??

I think it's useful, in order to make that evaluation, to allow this
hiden file. I don't think it's a big burden for me, and don't expect
anyone else to maintain it.

On Wed, 26 Apr 2017 22:55:48 +0200 dptd dptd <dptdescribe@gmail.com> wrote: 

dd> Sorry for asking stupid questions but… is this some kind of
“official” emacs mirror on gitlab? dd> What is the purpose of it?

Not an official anything. Just a way to evaluate Gitlab CI against
Hydra, Buildbot, and other CI solutions.

Ted




  parent reply	other threads:[~2017-04-27 16:16 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
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 [this message]
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=87zif1n7vl.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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).