[pkg-bacula-devel] Testing Salsa-CI for Bacula

Sven Hartge sven at svenhartge.de
Sun Nov 11 20:42:40 GMT 2018

On 10.11.18 22:16, Sven Hartge wrote:
> Hi!
> > Following the announcement about the CI pipeline on Salsa I thought
> "neat, this can be useful".
> And immediately after enabling it, I ran into an issue: QT5/rcc uses the
> statx syscall, which is not whitelisted on the Docker systems Salsa uses
> to run the builds etc.

OK, I figured this out now. Needed a bit of force to beat the systems
into submission, but it works now. Once the CI-Team has sorted out their
problems, the configuration will get simpler again.

But so far, after every push, the CI pipeline builds the packages and
runs lintian on them, mailing a report after it is done.

I hope this will help spot possible issues earlier.

I might even get piuparts working later, but for now it tries to run its
checks on all packages at the same time, including all conflicting
database flavors, causing the tests to fail of course.

This needs some manual intervention to keep this from happening.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-bacula-devel/attachments/20181111/5b023144/attachment.sig>

More information about the pkg-bacula-devel mailing list