-
Notifications
You must be signed in to change notification settings - Fork 619
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
Comments
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? |
Would be blocked until we have v4 API support. #530. |
is anyone interested in submitting a PR ? |
Any news on this? |
+1 would be interested in this as well |
Any updates here? This prevents us from implementing a solid merge-request & code coverage focused microservice architecture. |
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 |
+1 for this |
Interested as well. Thanks for the investigation |
Fix for stale ghprbCommentBody values (jenkinsci#233/JENKINS-40802)
Hi, any update on this? |
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
The text was updated successfully, but these errors were encountered: