Re: The CI issue (was Re: Request push access on Salsa)

2021-10-18 Thread Faustin Lammler
Aloïs Micard , 18/10/2021 – 18:33:14 (+0200): > Since we try to keep only one version of a package at a given time, > every package upload may break other packages that depends on it. This > is especially true for Go core package. > > While we could use a standards workflow and use tools like > d

Re: The CI issue (was Re: Request push access on Salsa)

2021-10-18 Thread Aloïs Micard
On 10/18/21 6:26 PM, Nilesh Patra wrote: Hi Faust, On Mon, 18 Oct, 2021, 9:43 pm Faustin Lammler, wrote: > To put it in a nutshell: we have a very special setup that allows us > to prevent any regression (efficiently) with all go packages currently > on the archive. But this set

Re: The CI issue (was Re: Request push access on Salsa)

2021-10-18 Thread Nilesh Patra
Hi Faust, On Mon, 18 Oct, 2021, 9:43 pm Faustin Lammler, wrote: > > To put it in a nutshell: we have a very special setup that allows us > > to prevent any regression (efficiently) with all go packages currently > > on the archive. But this setup requires a dedicated machine. That's > > why we c

Re: The CI issue (was Re: Request push access on Salsa)

2021-10-18 Thread Aloïs Micard
On 10/18/21 6:13 PM, Faustin Lammler wrote: Also, the fact that the go team should provide personal runners seems a bit strange to me and I am wondering why those can not be provided by Debian infra... But again, I am maybe lacking information here. Before asking DSA [1] for a dedicated machi

Re: The CI issue (was Re: Request push access on Salsa)

2021-10-18 Thread Faustin Lammler
Hi! Aloïs Micard , 18/10/2021 – 17:26:27 (+0200): > Please see the page dedicated to our CI setup [1] for more details, > everything is explained. I did it but see bellow. > To put it in a nutshell: we have a very special setup that allows us > to prevent any regression (efficiently) with all go

Re: The CI issue (was Re: Request push access on Salsa)

2021-10-18 Thread Nilesh Patra
> I'll setup a VM on my infra and try to follow your setup documentation so I may have more feedback in the next days. Why not instead take up a shell account on Aloïs's machine instead? :) Thanks a lot for helping out with this in any case! Nilesh

Re: The CI issue (was Re: Request push access on Salsa)

2021-10-18 Thread Aloïs Micard
Hello Faustin, On 10/18/21 5:02 PM, Faustin Lammler wrote: The thing is, the runner managed by @stapbelerg is down because he's moving off Debian [2] and therefore has put the machine to another use. Why not using salsa shared runners and all the work made by the SalsaCI Team? Sorry if this was

Re: The CI issue (was Re: Request push access on Salsa)

2021-10-18 Thread Faustin Lammler
Nilesh Patra , 18/10/2021 – 08:11:54 (-0700): > > I'll setup a VM on my infra and try to follow your setup documentation > so I may have more feedback in the next days. > > Why not instead take up a shell account on Aloïs's machine instead? :) Because this would not validate the setup documentat

Re: The CI issue (was Re: Request push access on Salsa)

2021-10-18 Thread Faustin Lammler
Hi Aloïs! Aloïs Micard , 15/10/2021 – 16:39:59 (+0200): > In the go team we have a kinda 'special' CI setup put in place by @stapelberg > which greatly improve the life of Go maintainers by doing full rebuild of all > go packages at every commit. This way you know exactly if your new commit > int

The CI issue (was Re: Request push access on Salsa)

2021-10-15 Thread Aloïs Micard
On 10/14/21 11:38 AM, Faustin Lammler wrote: Hi! Aloïs Micard , 14/10/2021 – 11:02:17 (+0200): The CI has been disabled for the whole Go packages. (I'm still working on getting the runner fixed) I would be happy to help you on that task. I have quite good experience with CI systems (drone.io