Re: GitLab CI setup file in scratch/tzz/gitlab

[Mike Gerwitz <mtg@gnu.org>]

[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]

On Fri, Apr 28, 2017 at 17:33:54 -0400, Richard Stallman wrote:
> If we install files to enable people to use a variety of CI sites,
> including GitLab among them might not matter.
>
> However, to install just one file for one site is tantamount to
> selecting that as "the" CI site for Emacs.  As has been pointed out,
> using GitLab for this purpose would be SaaSS.

That file would be recognized by _any_ Gitlab instance, including
self-hosted.  Of course, that also means it would be recognized by
Gitlab.com's own instance.  I've used Gitlab's pipelines self-hosted,
but haven't on Gitlab.com, so I don't know if it needs to be explicitly
enabled or if it automatically takes effect.

My point being: the presence of that file doesn't itself imply SaaSS in
the case of Gitlab.  But it might be worth documenting that fact
explicitly somewhere.

In the case of a service like Travis CI, though, I think that's only
available as SaaSS via GitHub---I haven't heard of anyone self-hosting
it, though it seems like it might technically be possible to do so.[0]
Therefore I think that a Travis configuration file would effectively be
endorsing its SaaSS service.

-- 
Mike Gerwitz
Free Software Hacker+Activist | GNU Maintainer & Volunteer
GPG: D6E9 B930 028A 6C38 F43B  2388 FEF6 3574 5E6F 6D05
https://mikegerwitz.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]