Pre-review CI

[Bhushan Shah]

Hello,

So in previous email about staging repository I talked about pre-review
CI [1]. After some time, we finally have some code in ci-tooling which can
handle the pre-review CI for KDE repositories. And for initial pilot run
we want to enable it for frameworks repositories.

We have several questions about this though,

- Should we have seperate CI jobs per platform (Linux, Windows, FreeBSD,
  Android) for review? or just 1 job which runs the builds across all
  platforms?
- Should we send out comment for failure and success? Or is it easier to
  figure out the console log link without the comment? See linked review
  for example [1].

Looking forward to feedback.

Thanks!

[1] https://mail.kde.org/pipermail/kde-frameworks-devel/2018-June/065616.html
[2] https://phabricator.kde.org/D14438

-- 
Bhushan Shah
http://blog.bshah.in
IRC Nick : bshah on Freenode
GPG key fingerprint : 0AAC 775B B643 7A8D 9AF7 A3AC FE07 8411 7FBC E11D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20180729/94f959d8/attachment.sig>