Mark the repo as unmaintained and archive it

[fatso83]

Even though this seems like the most frequently updated package for Jest teamcity reporters, this repo has not been updated since 2018, PRs are lying dormant and the docs are outdated. It would be better if this was clearly marked on the front page, possibly linking to alternatives like an actively updated alternative like jest-teamcity (15 K downloads/week) or a package that simply uses the JUnit compatible output (like jest-junit (about 1.6 M downloads/week)

[Maxim-Zabunkov]

HI there, we still use this package and recently found an issue I checked proposed jest-teamcity and figured out it lacks code coverage reporting code - so it simply does not fit

[fatso83]

@Maxim-Zabunkov Code coverage is generated by jest itself and jest-junit does a fine job of creating the junit xml files.

When running jest --ci --coverage I get a nice coverage-final.json JSON file with stats on each file. This is built-in.

[Maxim-Zabunkov]

@fatso83, looks like you did't understand the gap I mentioned. TeamCity has a built-in ability to render code coverage stats in overview + it collects historical trends. So we need to post those stats using service messages and TeamCity will take care of the rest. jest-teamcity plugin should post those data from generated jest coverage results.

[fatso83]

Probably right about that. We had stopped using TC by the time I created that last comment anyhow 😄