Feature request: TeamCity inspection format output about dependency-cruiser HOT 4 CLOSED

Thanks again for the validation & suggestions during development - [email protected] with this feature should be on npm in a few minutes.

from dependency-cruiser.

hi @ulrichb thanks for the suggestion! I see the benefits of output that is easy to navigate in a CI as well, so I'll look into this (later this week, likely). I have never used team city yet - so I'll need some help with the validation

The reporter mechanism is made to be easily extensible (though not pluggable (yet) - the html and dot output to wit) so adding a new reporter (or 'formatter' as eslint calls it) should be fairly straightforward.

from dependency-cruiser.

Okay, cool!

so I'll need some help with the validation

Np. Can test it for you and send some screens.

from dependency-cruiser.

hi @ulrichb - [email protected] now has a teamcity reporter - see #138 for details. It'd be great if you could give it a spin and let me know how it works for you.

As you can see in the PR I have one doubt - the reporter logs all rules as inspectionType. This is correct if the collection of inspectionTypes functions as a reference table - which is what I inferred from the documentation. It could be that in practice it just generates noise in the TeamCity feedback. If that's indeed happening, let me know - it's a fairly small adjustment.

I'd also like to report the number of violations found - but maybe TeamCity is doing that itself already?

There's a PR for an eslint-json reporter as well, but it's not in the published version.
I'm going to kick it out a.o. as the goal was to make a reporter for TeamCity anyway,

from dependency-cruiser.