8 ms·

GitLab product director for CI/CD here - thanks so much for the feedback, everyone. It's really great to read how much you're getting value out of what we built

GitLab product director for CI/CD here - thanks so much for the feedback, everyone. It's really great to read how much you're getting value out of what we built. We have an overall CI/CD direction page up at https://about.gitlab.com/direction/cicd https://about.gitlab.com/direction/cicd which you can drill down into the individual stages plans from. Feedback is always welcome, we love building things in partnership with real users. You can reach me at jason@gitlab.com any time.

kuschku 7y ago
Have you started working on providing a UI for the XML test result artifacts produced in CI runs? They are displayed in merge requests but not anywhere in the normal CI pipeline UI and I'd live to be able to see those and see what works and what doesn't.
- boleary-gl 7y ago
  GitLab Product Manager for Verify (CI) here (who works for the Director above ). Yes - that's something we want to get to this year. We call it "CI Views" right now but we want to expose better all the types of test results that get collected by GitLab. Today for XML (JUnit) results, you can see what fails in the merge request with https://docs.gitlab.com/ee/ci/junit_test_reports.html https://docs.gitlab.com/ee/ci/junit_test_reports.html. But we want to make the XML, JSON or HTML output of _any_ type of test first class with CI Views: https://gitlab.com/gitlab-org/gitlab-ce/issues/35379 https://gitlab.com/gitlab-org/gitlab-ce/issues/35379
  - kuschku 7y ago
    Yes, but that only works for the merge request view so far, are there plans to add a view of these to each CI job, so even if something on master fails, I can see the results?
    - boleary-gl 7y ago
      Not sure if it will make the first iteration (as merge request centric workflow will be "first")...but I agree the vision should include the ability to see the tests on any pipeline.

8 ms·

GitLab product director for CI/CD here - thanks so much for the feedback, everyone. It's really great to read how much you're getting value out of what we built

by jl-gitlab 7y ago

kuschku 7y ago
Have you started working on providing a UI for the XML test result artifacts produced in CI runs? They are displayed in merge requests but not anywhere in the normal CI pipeline UI and I'd live to be able to see those and see what works and what doesn't.
- boleary-gl 7y ago
  GitLab Product Manager for Verify (CI) here (who works for the Director above ). Yes - that's something we want to get to this year. We call it "CI Views" right now but we want to expose better all the types of test results that get collected by GitLab. Today for XML (JUnit) results, you can see what fails in the merge request with https://docs.gitlab.com/ee/ci/junit_test_reports.html https://docs.gitlab.com/ee/ci/junit_test_reports.html. But we want to make the XML, JSON or HTML output of _any_ type of test first class with CI Views: https://gitlab.com/gitlab-org/gitlab-ce/issues/35379 https://gitlab.com/gitlab-org/gitlab-ce/issues/35379
  - kuschku 7y ago
    Yes, but that only works for the merge request view so far, are there plans to add a view of these to each CI job, so even if something on master fails, I can see the results?
    - boleary-gl 7y ago
      Not sure if it will make the first iteration (as merge request centric workflow will be "first")...but I agree the vision should include the ability to see the tests on any pipeline.