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

Generate jacoco xml report #2652

Merged
merged 1 commit into from
May 27, 2024
Merged

Generate jacoco xml report #2652

merged 1 commit into from
May 27, 2024

Conversation

parapluplu
Copy link
Contributor

For some build processes the xml file is better integrated (e.g. if you need to transform the jacoco report to a cobertura report). So far only the csv report was generated.

For some build processes the xml file is better integrated (e.g. if you need to transform the jacoco report to a cobertura report).
So far only the csv report was generated.
@sfeilmeier sfeilmeier merged commit 9a76f7a into OpenEMS:develop May 27, 2024
@sfeilmeier
Copy link
Contributor

Thank you! Can you share more information about your cobertura reports and how you integrate OpenEMS with it? Could it be adopted by our CI pipeline? I would appreciate to discuss this on https://community.openems.io/

@parapluplu parapluplu deleted the patch-1 branch June 5, 2024 10:18
@parapluplu
Copy link
Contributor Author

Hey, thanks for the quick merge.

I'm working at Voltfang (my real name is Felix Remmel) and we're currently setting up our own CI/CD infrastructure. Since we're using gitlab as platform, processes are slightly different than for github. This change is required, so we're able to see code coverage in code reviews and for pipeline builds.

I'm super happy to discuss this https://community.openems.io/, but for now I don't have anything specific to discuss, since we're still building up things. If you know any topic that fits to what we're doing, I'm happy if you send me a link.

This is an awesome project and I'm very happy to be able to work on it! Thanks so much for all the effort you and the community put into this.

@sfeilmeier
Copy link
Contributor

Hey Felix, thanks for the insights.

For your consideration, we use

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

Successfully merging this pull request may close these issues.

2 participants