Hi all
[Resending as apparently it didn't reach most of you due to Gmail rejecting my mails.]
For quite some time we're using Jenkins for CI. We've also added Travis during next the years. Do you think it's reasonable to still have both of them?
Own Jenkins server requires some maintenance and currently doesn't integrate that well with GitHub as Travis. This could be probably addressed, but the questions is whether it's worth of it.
My personal opinion is that Jenkins does not really have any benefits, so maybe it's time to drop it from our infrastructure.
PS: I've disabled error-reporting-server tests there as they are apparently failing due to some timezone errors.
On Sat, Jun 3, 2017 at 4:42 AM, Michal Čihař michal@cihar.com wrote:
Hi all
[Resending as apparently it didn't reach most of you due to Gmail rejecting my mails.]
For quite some time we're using Jenkins for CI. We've also added Travis during next the years. Do you think it's reasonable to still have both of them?
Own Jenkins server requires some maintenance and currently doesn't integrate that well with GitHub as Travis. This could be probably addressed, but the questions is whether it's worth of it.
My personal opinion is that Jenkins does not really have any benefits, so maybe it's time to drop it from our infrastructure.
PS: I've disabled error-reporting-server tests there as they are apparently failing due to some timezone errors.
-- Michal Čihař | https://cihar.com/ | https://weblate.org/
Hi,
I find the Checkstyle, JSLint, PMD reports from Jenkins quite useful in improving code quality. I am not sure whether these are avaialble with Travis.
Other than that I do not see any other reason to keep Jenkins server.
Hi
Madhura Jayaratne píše v Ne 04. 06. 2017 v 11:00 +1000:
I find the Checkstyle, JSLint, PMD reports from Jenkins quite useful in improving code quality. I am not sure whether these are avaialble with Travis.
Good point. Some of these are present on Scrutinizer (https://scrutiniz er-ci.com/g/phpmyadmin/phpmyadmin/) or Codacy (https://www.codacy.com/a pp/nijel/phpmyadmin/), though it probably doesn't cover them all.
Hi
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.
We can review the current Travis configuration and add more code quality tools, if necessary.
Maurício Meneghini Fauth
On Tue, Jun 6, 2017 at 5:31 AM, Michal Čihař michal@cihar.com wrote:
Hi
Madhura Jayaratne píše v Ne 04. 06. 2017 v 11:00 +1000:
I find the Checkstyle, JSLint, PMD reports from Jenkins quite useful in improving code quality. I am not sure whether these are avaialble with Travis.
Good point. Some of these are present on Scrutinizer (https://scrutiniz er-ci.com/g/phpmyadmin/phpmyadmin/) or Codacy (https://www.codacy.com/a pp/nijel/phpmyadmin/), though it probably doesn't cover them all.
-- Michal Čihař | https://cihar.com/ | https://weblate.org/
Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
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/
Hi
Our Jenkins is currently not working well due to following issue:
https://issues.jenkins-ci.org/browse/JENKINS-46357
-
Madhura Jayaratne -
Maurício Meneghini Fauth -
Michal Čihař