[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: management of debian/salsa-ci.yml (Was: Why is the team standard to use two-file includes for Salsa CI?)



On 15/08/25 at 15:11 -0700, Soren Stoutner wrote:
> On Thursday, August 14, 2025 11:11:08 PM Mountain Standard Time Lucas Nussbaum 
> wrote:
> > I wonder if the should centralize CI configuration, using something
> > like:
> > ------------------------>8
> > ---
> > include:
> >   - https://salsa.debian.org/ruby-team/meta//raw/master/salsa-ci.yml
> > ------------------------>8
> > 
> > This would allow us to use defaults that differ from salsa-ci-team's
> > (centrally enable a job that is disabled by default) or add a custom,
> > team-specific job. What do you think?
> 
> I would be fine with that.  However, up until the point that we have an 
> accepted, centralized Ruby Team CI configuration, I think we should follow the 
> default recommended Salsa CI configuration unless there is a good reason to 
> make modifications.  As such, I would recommend reverting this commit:
> 
> https://salsa.debian.org/ruby-team/redmine/-/commit/ 
> d0af6274cf5cb42deb13a536ee0802fb64b01172

Hi Soren,

To make sure we are on the same page:
Do you agree that this would not result in any change in the way the
package is tested, given the content of
https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/recipes/debian.yml
? And that it would only result in making redmine a special case again
among Ruby packages, since it would be the only one with that CI config?

Lucas


Reply to: