Hi Carsten, Hi List,
Le Fri, Sep 23, 2022 at 07:01:05AM +0200, Carsten Schoenert a écrit :
> heavily force pushing to not blow up the git tree with dozens of Fixup
> commits! In the 'official' git tree this is a no go of course.
Would doing the work in a git branch and 'git merge --squash' at
Hi Carsten (2022.09.23_05:01:05_+)
> sure, that's a killer argument that I can't really argue against. But that
> is not the point for me.
>
> For all these checks we already have existing infrastructure, running the
> same also by a pipeline job isn't helping at all if it's not clear how to
Hello Emanuele,
Am 21.09.22 um 12:01 schrieb Emanuele Rocca:
Well but that's the whole point of automated testing. There's no *need*
to do it locally if it's already done by Salsa for you. What is already
automated and working pretty well is:
- amd64 build
- i386 build
- source build
-
> Well but that's the whole point of automated testing. There's no *need*
> to do it locally if it's already done by Salsa for you. What is already
> automated and working pretty well is:
>
> - amd64 build
> - i386 build
> - source build
> - autopkgtest
> - blhc
> - lintian
> - piuparts
> -
Emanuele Rocca writes:
> What's wrong with pushing your work before uploading to ftp-master
> instead? :-)
I am learning to do this with my packages.
Because otherwise, when I push to get, I often find I forgot to do a
pull beforehand, and there are changes in salsa that are not reflected
in
Hi,
Le 20/09/2022 à 17:35, Carsten Schoenert a écrit :
Hi,
Am 20.09.22 um 16:13 schrieb Emanuele Rocca:
Salsa CI is useful because it automatically performs binary/source
builds,
arm64 crossbuilds, and it runs various pretty important tests such as
lintian,
piuparts, reproducible build
Hello,
Emanuele Rocca, le mer. 21 sept. 2022 12:01:21 +0200, a ecrit:
> The only work left to be done on your machine is a binary build to see
> if the packages look good, perhaps some specific manual testing [1],
>
> [1] though that may be an opportunity for writing a new autopkgtest!
Yes,
Hi,
On 2022-09-20 03:09, Sandro Tosi wrote:
> the vast majority of the team members (based on the commits email i
> receive) are uploading the package to the archive at the same time as
> they are pushing a full set of changes to salsa (and sometimes only
> *after* the package has been ACCEPTED);
Hallo Carsten,
On 2022-09-20 05:35, Carsten Schoenert wrote:
> Am 20.09.22 um 16:13 schrieb Emanuele Rocca:
> > Salsa CI is useful because it automatically performs binary/source builds,
> > arm64 crossbuilds, and it runs various pretty important tests such as
> > lintian,
> > piuparts,
> Am 20.09.22 um 16:13 schrieb Emanuele Rocca:
> > Salsa CI is useful because it automatically performs binary/source builds,
> > arm64 crossbuilds, and it runs various pretty important tests such as
> > lintian,
> > piuparts, reproducible build testing, and more. It also runs autopkgtest in
> >
Hi,
Am 20.09.22 um 16:13 schrieb Emanuele Rocca:
Salsa CI is useful because it automatically performs binary/source builds,
arm64 crossbuilds, and it runs various pretty important tests such as lintian,
piuparts, reproducible build testing, and more. It also runs autopkgtest in
LXC.
quite
Hi Sandro,
On Tue, Sep 20, 2022 at 08:31:14AM -0400, Sandro Tosi wrote:
> the way i worded my initial question was so that you could list the
> reasons that make it so useful, in detail: so would you like to do?
Salsa CI is useful because it automatically performs binary/source builds,
arm64
On Tue, Sep 20, 2022 at 4:33 AM Emanuele Rocca wrote:
> On 19/09 02:14, Sandro Tosi wrote:
> > what would the team get out of doing this?
>
> The way I see it, CI on Salsa is so useful that it should be enabled by
> default unless there are good reasons not to.
the way i worded my initial
Hi Sandro,
On 19/09 02:14, Sandro Tosi wrote:
> what would the team get out of doing this?
The way I see it, CI on Salsa is so useful that it should be enabled by
default unless there are good reasons not to.
ciao,
Emanuele
> I was wondering if it would make sense to enable CI/CD on Salsa for all
> projects owned by the Debian Python Team, or if there's any concern
> about scaling issues in terms of pipeline workers (or anything else
> really).
what would the team get out of doing this?
--
Sandro "morph" Tosi
My
On 2022-09-19 06 h 51, Emanuele Rocca wrote:
Hello debian-salsa-ci and debian-python!
I was wondering if it would make sense to enable CI/CD on Salsa for all
projects owned by the Debian Python Team, or if there's any concern
about scaling issues in terms of pipeline workers (or anything else
16 matches
Mail list logo
