[Phpmyadmin-devel] Skipping Travis CI & Scrutinizer CI builds for weblate pushes

[Chirayu Chiripal]

On Tue, Aug 12, 2014 at 3:02 PM, Michal Čihař <michal at cihar.com> wrote:

> Hi
>
> Dne Tue, 12 Aug 2014 14:49:53 +0530
> Chirayu Chiripal <chirayu.chiripal at gmail.com> napsal(a):
>
> > Coveralls is considering such PR's as first build on master (targeted
> > branch), maybe because coveralls sees that latest commit on master is not
> > having coverage report but those changes are in po files only and he
> should
> > be interested only in libraries/ directory (see [1]).
> >
> > [1]: https://coveralls.io/builds/1038671
>
> Indeed this is caused by Coveralls not skipping these commits. Maybe we
> could use just Scrutinizer as it reports coverage too?
>
> > Scrutinizer cancels inspection due to some mismatch parent commits error
> > (see [2]). I think scrutinizer behavior is kind of a bug.
> >
> > [2]:
> >
> https://scrutinizer-ci.com/g/phpmyadmin/phpmyadmin/inspections/963075d0-558f-4a6f-a17e-317021793d13
>
> In this case it's IMHO not related - it's just that the pull request
> has been updated between the build has been scheduled and it has
> started. These did happen before as well.
>

Lets take another inspection [3]. This PR was never updated once it was
created and the only inspection was this [3].

[3]:
https://scrutinizer-ci.com/g/phpmyadmin/phpmyadmin/inspections/6f395762-0afe-4d75-8784-7ea96a697147
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.phpmyadmin.net/pipermail/developers/attachments/20140812/0116320b/attachment.html>