Re: Streamlining the use of Salsa CI on team packages

2019-10-15 Thread Peter Pentchev
On Mon, Oct 14, 2019 at 01:51:57PM +, PICCA Frederic-Emmanuel wrote: > Hello, > > and if at the end the upstream could take care of the Debian packaging, by > adding a > .salsa-ci.yml in the upstream directory, in order to have a feedback with > nice badges ? That would mean that part of

Re: Streamlining the use of Salsa CI on team packages

2019-10-14 Thread Thomas Goirand
On 9/16/19 10:03 PM, Hans-Christoph Steiner wrote: >>> I know the Ruby team also decided to use debian/salsa-ci.yml instead of >>> debian/gitlab-ci.yml [2]. I guess we should also do the same. > This is still an open question: > https://salsa.debian.org/salsa-ci-team/pipeline/issues/86 > > Debian

Re: Streamlining the use of Salsa CI on team packages

2019-10-11 Thread Louis-Philippe Véronneau
On 19-09-15 20 h 31, Louis-Philippe Véronneau wrote: > On 19-09-05 01 h 40, Louis-Philippe Véronneau wrote: >> Hello folks! >> >> I'd like to propose we start using Salsa CI for all the team packages. I >> think using a good CI for all our packages will help us find packaging >> bugs and fix

Re: Streamlining the use of Salsa CI on team packages

2019-09-17 Thread Hans-Christoph Steiner
Raphael Hertzog: > Hi, > > On Sun, 15 Sep 2019, Louis-Philippe Véronneau wrote: >> For step 1, I proposed we use the "Salsa Pipeline" [1], as I feel it is >> the most mature solution, has more contributors and has more features >> (including reprotest and piuparts). This option seems to have had

Re: Streamlining the use of Salsa CI on team packages

2019-09-17 Thread Raphael Hertzog
Hi, On Sun, 15 Sep 2019, Louis-Philippe Véronneau wrote: > For step 1, I proposed we use the "Salsa Pipeline" [1], as I feel it is > the most mature solution, has more contributors and has more features > (including reprotest and piuparts). This option seems to have had the > most support so far.

Re: Streamlining the use of Salsa CI on team packages

2019-09-16 Thread Hans-Christoph Steiner
Louis-Philippe Véronneau: > On 19-09-05 01 h 40, Louis-Philippe Véronneau wrote: >> Hello folks! >> >> I'd like to propose we start using Salsa CI for all the team packages. I >> think using a good CI for all our packages will help us find packaging >> bugs and fix errors before uploads :) >>

Re: Streamlining the use of Salsa CI on team packages

2019-09-16 Thread Marcin Kulisz
On 15 September 2019 23:01:46 BST, Thomas Goirand wrote: snip >This tells "instance_type: g1-small", which doesn't match any name at: >https://cloud.google.com/compute/vm-instance-pricing > >Am I right that this is n1-standard-1, which is 1 VCPU and 3.75 GB? Nop, this is incorrect you're

Re: Streamlining the use of Salsa CI on team packages

2019-09-15 Thread Louis-Philippe Véronneau
On 19-09-05 01 h 40, Louis-Philippe Véronneau wrote: > Hello folks! > > I'd like to propose we start using Salsa CI for all the team packages. I > think using a good CI for all our packages will help us find packaging > bugs and fix errors before uploads :) > > I also think that when possible,

Re: Streamlining the use of Salsa CI on team packages

2019-09-15 Thread Louis-Philippe Véronneau
On 19-09-15 18 h 01, Thomas Goirand wrote: > On 9/15/19 4:10 AM, Louis-Philippe Véronneau wrote: >> On 19-09-14 17 h 35, Thomas Goirand wrote: >>> On 9/13/19 11:08 PM, Louis-Philippe Véronneau wrote: On 19-09-13 05 h 57, Thomas Goirand wrote: > On 9/5/19 7:40 AM, Louis-Philippe Véronneau

Re: Streamlining the use of Salsa CI on team packages

2019-09-15 Thread Thomas Goirand
On 9/15/19 4:10 AM, Louis-Philippe Véronneau wrote: > On 19-09-14 17 h 35, Thomas Goirand wrote: >> On 9/13/19 11:08 PM, Louis-Philippe Véronneau wrote: >>> On 19-09-13 05 h 57, Thomas Goirand wrote: On 9/5/19 7:40 AM, Louis-Philippe Véronneau wrote: > Hello folks! > > I'd like to

Re: Streamlining the use of Salsa CI on team packages

2019-09-14 Thread Thomas Goirand
On 9/13/19 11:08 PM, Louis-Philippe Véronneau wrote: > On 19-09-13 05 h 57, Thomas Goirand wrote: >> On 9/5/19 7:40 AM, Louis-Philippe Véronneau wrote: >>> Hello folks! >>> >>> I'd like to propose we start using Salsa CI for all the team packages. I >>> think using a good CI for all our packages

Re: Streamlining the use of Salsa CI on team packages

2019-09-13 Thread Louis-Philippe Véronneau
On 19-09-13 05 h 57, Thomas Goirand wrote: > On 9/5/19 7:40 AM, Louis-Philippe Véronneau wrote: >> Hello folks! >> >> I'd like to propose we start using Salsa CI for all the team packages. I >> think using a good CI for all our packages will help us find packaging >> bugs and fix errors before

Re: Streamlining the use of Salsa CI on team packages

2019-09-13 Thread Thomas Goirand
On 9/5/19 7:40 AM, Louis-Philippe Véronneau wrote: > Hello folks! > > I'd like to propose we start using Salsa CI for all the team packages. I > think using a good CI for all our packages will help us find packaging > bugs and fix errors before uploads :) I would agree *IF* and only *IF* we find

Re: Streamlining the use of Salsa CI on team packages

2019-09-12 Thread Louis-Philippe Véronneau
On 19-09-10 14 h 09, Hans-Christoph Steiner wrote: > > > Gregor Riepl: >> >>> I am not a fan of pointing to a moving target with the "include" statement: >>> >>> include: >>> - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml >>> - >>>

Re: Streamlining the use of Salsa CI on team packages

2019-09-10 Thread Hans-Christoph Steiner
Gregor Riepl: > >> I am not a fan of pointing to a moving target with the "include" statement: >> >> include: >> - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml >> - >> https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml >> >> "master"

Re: Streamlining the use of Salsa CI on team packages

2019-09-05 Thread Gregor Riepl
> I am not a fan of pointing to a moving target with the "include" statement: > > include: > - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml > - > https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml > > "master" will change, and that can

Re: Streamlining the use of Salsa CI on team packages

2019-09-05 Thread Hans-Christoph Steiner
I think we should definitely use Gitlab-CI! The 'salsa-ci-team/pipeline' project does have good coverage, with reprotest and piuparts. I'm the lead dev on another approach, also part of the salsa-ci-team, called 'ci-image-git-buildpackage':