Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,763
    • Issues 44,763
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,329
    • Merge requests 1,329
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #202525
Closed
Open
Issue created Feb 06, 2020 by Mark Lapierre@mlapierreMaintainer

Make Junit reports accessible via the API

Problem to solve

JUnit reports are only accessible via the UI, which means reports in non-public pipelines can't be downloaded without authenticating via the UI.

Artifacts from individual jobs can be downloaded, but that is inefficient when a compiled report is required.

Intended users

Quality will start using it immediately.

  • Delaney (Development Team Lead)
  • Sasha (Software Developer)

Further details

Quality want to use the test report to automatically create/update issues in our testcases project to assist with test case management until we have a more complete solution.

Proposal

Add an API route to fetch test reports for a given pipeline.

I.e., GET /projects/:id/pipelines/:pipeline_id/test_report

Permissions and Security

Probably the same permissions used for access to pipelines themselves.

Documentation

Add the route to the Pipelines API page

Availability

The JUnit report feature is currently off by default due to performance issues, which will be fixed in #37725 (closed)

Until then the new API route should also be behind the same feature flag as the full feature.

Testing

It will require new tests in spec/requests/api/pipelines_spec.rb

Links / references

&1875 (closed)

Assignee
Assign to
Time tracking