Usage pattern for automated CI builds/report generation? #53
Description
How are folks using cssstats in an automated, CI environment? I'd love to integrate this into my gulp build that gets run on Jenkins. I could get a consumable report I could point to which is always up to date, similar to our code coverage reports, ESLint statistics, etc.
But I'm not sure how to do it; every approach I can think of has some limitations.
Right now running the gulp task & generating JSON doesn't help visualize the way we'd want. The cssstats-webapp requires a node server to be running, while we'd prefer static HTML. And I don't think there are any Jenkins or other CI plugins that know how to consume the JSON report.
Are you aware of anyone who's doing this well?
Related: this issue makes it look like there's some interest in an HTML report.