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

[Dmitry Gutov]

On 27.04.2017 17:59, Eli Zaretskii wrote:

> > It sounds silly. We should have an accessible, friendly CI instance for
> > all our users.
>
> I don't understand this attack.  We didn't yet decide that this site
> will be our CI site.

If we don't like it, we can easily delete the file. It's low-conflict, 
low-maintenance. There's almost zero cost to adding it.

Further, the contents of the file are not tied to the "site", just to 
GitLab as a project. It can be used by other GitLab installations 
without changes.

> Until we do, why should we function as someone
> else's repository??

From that perspective, Ted has already done what you're asking 
(committed the change into a different repository).

The first message of this thread is a request to take a further step, to 
make a fair evaluation easier.

As a result of having this file in master, the GitLab instance will 
build all later branches that are pushed to the repository (with some 
possible exceptions).

I am restating here the second paragraph of that email, BTW.