Re: Salsa.d.o: Please support the implementation request for a global config option to change the default for "Custom CI config path" in Gitlab
- To: debian-devel@lists.debian.org
- Subject: Re: Salsa.d.o: Please support the implementation request for a global config option to change the default for "Custom CI config path" in Gitlab
- From: Inaki Malerba <inaki@malerba.space>
- Date: Thu, 1 Aug 2019 20:21:31 +0200
- Message-id: <[🔎] 9218004c-b5cd-2d0c-71c2-37dbe9a7ee39@malerba.space>
- In-reply-to: <20190727074029.rqecc7ta4fcltals@shell.thinkmo.de>
- References: <ca7c3bf877b6c3678e5a12d86ba1e6f7f73b5316.camel@debian.org> <20190726151702.4enc2kt5tiklqyqh@shell.thinkmo.de> <20190726170107.GA10350@espresso.pseudorandom.co.uk> <20190727074029.rqecc7ta4fcltals@shell.thinkmo.de>
On 27/7/19 09:40, Bastian Blank wrote:
> On Fri, Jul 26, 2019 at 06:01:07PM +0100, Simon McVittie wrote:
>> This was requested in the past in
>> https://salsa.debian.org/salsa/support/issues/26, and some people
>> (including me) interpreted the reply as "no, but only because upstream
>> doesn't have that feature". Was that interpretation wrong?
>
>> The default of ./.gitlab.yml is problematic for Salsa *because* it's
>> the upstream default, and git repositories on Salsa are most commonly
>> used for Debian packaging where we try to minimize delta vs upstream
>> source code:
>
> The setting is per project, so it is available. For now I say that
> changing this globally is too disruptive.
Of course it's a disruptive change, but what is the purpose of Salsa?
I think it's a tool *for* Debian and Debian Developers. Most of the
users surely will prefer that the default path for the CI configuration
on Debian projects is a Debian compatible path. Maybe we could open a
thread to discuss this on d-devel, if some day we have the feature to
make this change, but it's is not even planned yet.
Anyway, I think the best alternative for making this change less
disruptive is going to be group-level definitions[0] of this kind of
configurations.
Please, everyone interested on discussing this feature please comment
the issue on the Gitlab issue tracker.
0_ https://gitlab.com/gitlab-org/gitlab-ce/issues/41764#note_54911766
--
- ina
Reply to: