4 ms·

I have to use GitLab. But I really quite don’t get some features like: Multiple published html pages per job. Seems not possible: You have to have a special jo

by weitzj 6y ago

I have to use GitLab. But I really quite don’t get some features like: Multiple published html pages per job. Seems not possible: You have to have a special job name “pages” and your build artifacts have to be in a special directory “public” in order for this job to work correctly. Also collecting test coverage reports by grepping with a regex through your build stdout feels weird. These 2 examples leave a weird feeling - a feeling that some easily applicable features are just bolted onto GitLab and the underlying architecture is not capable of incorporating these features an a better way (multiple html websites, specialized coverage report parsers). Also extended/sharing pipelines between multiple teams without duplicating code or having stages “leaking into teams code” feels weird.

jamesh-gl 6y ago
GitLab PM here. Great point on #2 about the regex. We have an open issue (https://gitlab.com/gitlab-org/gitlab/-/issues/21549 https://gitlab.com/gitlab-org/gitlab/-/issues/21549) to parse more data from an uploaded coverage report and coverage percentage seems like a great first step so you don't have to mess around with the regex. -James H, GitLab Product Manager, Verify:Testing
- weitzj 6y ago
  It would be fine if you could for example pick up cobertura reports or maybe some other coverage formats (Golang reports, Xcode coverage reports) I know I can do this with all my Jenkins plug-ins. And maybe GitLab does not want to do all of this and people should use Sonarqube instead. But it is hard to go to GitLab when I have seen the light with Jenkins.
  - jamesh-gl 6y ago
    Cobertura is the first target report since it's the format that's supported by the Test Coverage Visualization feature (https://docs.gitlab.com/ee/user/project/merge_requests/test_coverage_visualization.html https://docs.gitlab.com/ee/user/project/merge_requests/test_...). I'll make sure the other report types are on our list of future iterations as well. Thanks! -James H, GitLab Product Manager, Verify:Testing

by weitzj 6y ago

jamesh-gl 6y ago

GitLab PM here. Great point on #2 about the regex. We have an open issue (https://gitlab.com/gitlab-org/gitlab/-/issues/21549 https://gitlab.com/gitlab-org/gitlab/-/issues/21549) to parse more data from an uploaded coverage report and coverage percentage seems like a great first step so you don't have to mess around with the regex. -James H, GitLab Product Manager, Verify:Testing

weitzj 6y ago
It would be fine if you could for example pick up cobertura reports or maybe some other coverage formats (Golang reports, Xcode coverage reports) I know I can do this with all my Jenkins plug-ins. And maybe GitLab does not want to do all of this and people should use Sonarqube instead. But it is hard to go to GitLab when I have seen the light with Jenkins.
- jamesh-gl 6y ago
  Cobertura is the first target report since it's the format that's supported by the Test Coverage Visualization feature (https://docs.gitlab.com/ee/user/project/merge_requests/test_coverage_visualization.html https://docs.gitlab.com/ee/user/project/merge_requests/test_...). I'll make sure the other report types are on our list of future iterations as well. Thanks! -James H, GitLab Product Manager, Verify:Testing