Support the ongoing development of Laravel.io →
posted 9 years ago
Laravel.io
Last updated 1 year ago.
0

Hey you should also try https://insight.sensiolabs.com/ from Sensio Labs. I have use it on a project and it was really good.

Last updated 1 year ago.
0

gafitescu said:

Hey you should also try https://insight.sensiolabs.com/ from Sensio Labs. I have use it on a project and it was really good.

Thanks! I added it to the list and updated my post a bit.

Last updated 1 year ago.
0

Hi Dries,

you might want to check out the config editor at https://scrutinizer-ci.com/config-editor which lets you put together your favorite checks (also includes checks for debug/commented code).

Cheers, Johannes

Disclaimer: I work there

Last updated 1 year ago.
0

Scrutinizer is nice... but in comparing it to Code Climate and Sensio Labs Insights, it's important to recognize that (at my last check) Scrutinizer is just bringing together pre-existing command line code insight tools, where Sensio Labs and Code Climate have custom analyses. (At least, I know Sensio does, and I think CodeClimate does.) However, they are great tools! Just note that you could, if you were really dedicated, reproduce all of Scrutinizer's insight by hand. I'd rather use Scrutinizer than do it manually, but Sensio has the added bonus of providing insight you couldn't get anywhere else...

I've gotten the most useful feedback from Sensio, moderately useful from Scrutinizer, and I've only brought two small repos into my CodeClimate account, but so far the feedback was almost useless. I'll have to try a much bigger site to know for sure, but CodeClimate was the only one of the three that didn't instantly give me a ton of opportunities to work... it just pointed out one obvious instance of duplication and called my code good otherwise.

Last updated 1 year ago.
0

Scrutinizer is bringing existing tools together (although some are from Scrutinizer itself) but I've had FAR better results with it than both Insights and Code Climate, exactly because of this reason : those are existing tools, tools that have matured for age and have been proven to work.

Last updated 1 year ago.
0

schmittjoh said:

Hi Dries,

you might want to check out the config editor at https://scrutinizer-ci.com/config-editor which lets you put together your favorite checks (also includes checks for debug/commented code).

Cheers, Johannes

Disclaimer: I work there

Hey Johannes, thanks for answering that. I didn't realise you could also indicate to check for those. I'll try to test that out later.

Last updated 1 year ago.
0

Hi Dries,

I work with Codacy, and we are also evolving in the same space: https://www.codacy.com/. We have a strong focus on PHP and have some great integrations with Github/Bitbucket/Gitlab (cloud or on-premise). We allow you, for example, to automatically receive the new issues introduced on every line of code directly in your Pull Request page. Let me know what you think. Best, Paul

Last updated 1 year ago.
0

FYI: in the mean time Code Climate has become my preferred tool. They've greatly extended their analysers and toolkit.

0

@driesvints: I like the fact that Code Climate has CLI which you can use on private projects

0

I recommend you take a look at the research "GitHub vs BitBucket vs GitLab" - https://www.cleveroad.com/blog/github-vs-bitbucket-vs-gitlab-developers-research

0

Sign in to participate in this thread!

JetBrains

Your banner here too?

Moderators

We'd like to thank these amazing companies for supporting us

Your logo here?

Laravel.io

The Laravel portal for problem solving, knowledge sharing and community building.

© 2023 Laravel.io - All rights reserved.