[Debian-med-packaging] [gitlab at salsa.debian.org: srst2 | Pipeline #196156 has failed for master | 31e29937]

[Étienne Mollier]

Hi Andreas,

Andreas Tille, on 2020-11-10 17:10:55 +0100:
> do you know how to silence Salsa-CI about
> 
>     srst2-build-deps : Depends: bowtie2 which is a virtual package and is not provided by any available package

When using the default debian/salsa-ci.yml from the template,
the package will import the configuration from files which are
considered sensible defaults per Salsa CI team appreciation.
There are two resources:

  * Tests in themselves are defined at the following location,
    and are actually a quite heavy piece of code:
	https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml

  * Description of the pipeline is on the following location,
    and seems much simpler:
	https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml

I would tend to believe we could remove the inclusion of the
pipeline-jobs.yml from our debian/salsa-ci.yml, and instead
inspire ourselves from the pipeline-jobs.yml to create our own
pipeline without known failing tests.  That would both ease work
load on Gitlab runners, and allow us to see regressions.

On the other hand, we may miss changes in the default pipeline.
I already had the opportunity to see changes there in the past
few months.

Should I see if I can get something working and not too hard to
maintain on srst2 repository?

Kind Regards,
-- 
Étienne Mollier <etienne.mollier at mailoo.org>
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/1, please excuse my verbosity.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/debian-med-packaging/attachments/20201110/22f4d8e4/attachment.sig>