Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is there a way to have multiple coverage services? #133

Open
joshrlesch opened this issue Feb 2, 2016 · 6 comments
Open

Is there a way to have multiple coverage services? #133

joshrlesch opened this issue Feb 2, 2016 · 6 comments

Comments

@joshrlesch
Copy link
Contributor

Is there a way to have multiple coverage services. For example:
slather coverage example.xcodeproject --coveralls --html

I hacked together something in my fork that is totally wrong and sucks because it regenerates the json output file but works. Just wondering if there is planning for this.

@neonichu
Copy link
Member

neonichu commented Feb 3, 2016

Why not just run twice, once per output format?

@joshrlesch
Copy link
Contributor Author

That is a valid and easy solution, but was just curious if that feature was something that would add value and maybe increase the performance instead of having to process the files multiple times. But if not many people would want that, then I can see not spending the time building that out.

I am good with closing this unless people want it open.

@Ashton-W
Copy link

Ashton-W commented Feb 5, 2016

I find not being able to support multiple outputs diminishes the value of the configuration file a bit. We always end up having to call slather with various flags multiple times.

I'm guessing it would be faster to do the outputs together too.

@yakimant
Copy link

yakimant commented Apr 8, 2016

I'd like to have simple output, html reports and teamcity service messages in one, if possible.

@tobilarscheid
Copy link

Our team was actually quite surprised that combining arbitrary output formats is not supported. Even if we are not implementing this feature, I feel slather should at least complain when multiple outputs formats are given as command line arguments. The current behaviour is very intransparent.

@aligermiyanoglu
Copy link

hey everyone, this could be a nice feature to add if there are no strong drawback out of it.
Basically, this could save a lot of build time(at the scale of thousands of hours) if we count Slather usage in the pipelines.
Our use case as follows, ~25 seconds of single job needs 3 times execution for different needs:

  • html output for developer views
  • json output for CI processing
  • sonarqube output to feed into Sonarqube.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants