Skip to content

GitLab Next

    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Menu
    Projects Groups Snippets
  • Sign up now
  • Login
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

GitLab 15.0 is launching on May 22! This version brings many exciting improvements, but also removes deprecated features and introduces breaking changes that may impact your workflow. To see what is being deprecated and removed, please visit Breaking changes in 15.0 and Deprecations.

  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #34102
Closed
Open
Created Jun 21, 2017 by Fabio Busatto@bikebillyContributor

Online view of HTML artifacts for public projects

Resources

Description

Many projects use CI for creating HTML/XML reports, for example in JUnit format. The Java Community is a clear example of that.

We want to support the online rendering and visualization of HTML artifacts that is currently unavailable on the artifacts browser because of security issues. Reports in other format (XML/JUnit) could be automatically translated into HTML by the proper tools, so they can be rendered too.

You can currently use GitLab Pages for this, but there are a few issues with this:

  • If your build already produces pages, then you have nowhere to put your test reports
  • If your project is not public, and you don't want your test reports to be public, then GitLab Pages will not work (they are always public)
  • From a usability perspective, this is not quite good enough. The usability should compare to how gitlab handles code coverage, which does not require GitLab Pages
  • But the biggest issue is that Pages only has one version of a published page, but you need to see test results for topic branches, old pipelines, etc.

Proposal

Using a separate domain in order to guarantee security, artifacts are published by CI and served online so they can be consumed directly from within the browser.

This iteration just focuses on the MVP, so there are just a subset of the features that could be implemented:

  • support for online display of HTML artifacts
  • automatic publishing from CI (similar to Pages)
  • support for public projects only
  • no authentication for user access
  • need for a separate domain (neither the same as the main instance of GitLab, nor Pages one)

Since we probably can't use an iframe or similar to display the HTML artifacts in the blob view, we'll need to open the HTML file separately. For this first iteration:

  • Change the link for HTML artifacts to open the HTML file in a new window/tab (instead of linking to the blob view)
  • Add a fa-external-link icon next to the HTML file name
  • Show the following tooltip next to the filename when hovering the whole table row: Opens in a new window

Links / references

  • Master meta issue: Improvements for Java language in CI (#33943 (moved))
  • Future iteration: Extend online view of HTML artifacts to private projects (#10982 (moved))

Documentation blurb

As many projects relies on GitLab for automatic testing, developers also need to access the test results in order to fully understand the feedback. With GitLab 9.5 we introduce the online browsing of HTML files created by pipelines, so your reports will be really simple to access directly from your browser.

Edited Sep 12, 2017 by Eric Eastwood
Assignee
Assign to
Time tracking