16 Jun
2017
16 Jun
'17
4:38 p.m.
Hi
Maurício Meneghini Fauth píše v Út 13. 06. 2017 v 21:52 -0300:
Jenkins is a powerful tool, but since it generates infrastructure costs, it's best not to use it. I think we can replace it completely with Travis.
I don't mind maintaining it as long as brings some additional value.
We can review the current Travis configuration and add more code quality tools, if necessary.
Scrutinizer should be able to cover most of the checks (at least it's already configured to use our coding standard):
https://scrutinizer-ci.com/g/phpmyadmin/phpmyadmin/
--
Michal Čihař | https://cihar.com/ | https://weblate.org/