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

Support reporting test coverage to gitlab merge requests #504

Open
keirlawson opened this issue Feb 15, 2017 · 11 comments
Open

Support reporting test coverage to gitlab merge requests #504

keirlawson opened this issue Feb 15, 2017 · 11 comments

Comments

@keirlawson
Copy link

Gitlab supports reporting test coverage through its merge request UI, and they have just exposed this functionality via their API: https://gitlab.com/gitlab-org/gitlab-ce/issues/27807

Would be great to have inbuilt support for deriving a test coverage figure from a jenkins job and updating gitlab accordingly

@mreichel
Copy link
Contributor

The feature is available in the Gitlab v4 API. To derive true test coverage one needs to use something like the Cobertura plugin. Jenkins has a so called health state (when you publish JUnit test results) that you can configure yourself. Would that be a option?

@omehegan
Copy link
Member

omehegan commented Jul 6, 2017

Would be blocked until we have v4 API support. #530.

@andrei-cacio
Copy link

is anyone interested in submitting a PR ?

@heppu
Copy link

heppu commented Oct 23, 2019

Any news on this?

@oolfloo
Copy link

oolfloo commented Apr 9, 2020

+1 would be interested in this as well

@Zahlii
Copy link

Zahlii commented Jan 20, 2021

Any updates here? This prevents us from implementing a solid merge-request & code coverage focused microservice architecture.

@timvahlbrock
Copy link

Maybe it would be even better to support uploading pipline artifacts to GitLab in General? As far as I know, the coverage reports are just a specialized type of pipeline artifact.

@timvahlbrock
Copy link

Maybe it would be even better to support uploading pipline artifacts to GitLab in General? As far as I know, the coverage reports are just a specialized type of pipeline artifact.

Which would be #486

@OBorce
Copy link

OBorce commented May 26, 2021

+1 for this

@builder-main
Copy link

Interested as well. Thanks for the investigation

exceed-alae pushed a commit to exceed-alae/gitlab-plugin that referenced this issue May 20, 2022
Fix for stale ghprbCommentBody values (jenkinsci#233/JENKINS-40802)
@kamilzajacdeviniti
Copy link

kamilzajacdeviniti commented Dec 28, 2022

Hi, any update on this?

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

No branches or pull requests