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

Sven Hartge sven at svenhartge.de
Mon Nov 12 17:16:52 GMT 2018

On 12.11.18 01:40, Sven Hartge wrote:
> On 12.11.18 00:57, Carsten Leonhardt wrote:
>> Sven Hartge <sven at svenhartge.de> writes:
>>> 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.
>> That's good, thanks :-)
> Correction: it only mails a report if anything fails.

Correction²: After enabling the CI integration to send mails to
dispatcher at tracker, a report is sent on failure and success.

If this gets too spammy, we can still flip it over to only sent a report
on failure.

But at least I like getting results pushed to me instead of having to
poll the Salsa webinterface manually.


-------------- 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/20181112/9452df8b/attachment.sig>

More information about the pkg-bacula-devel mailing list