I want to showcase the project I have been working on for the last weeks. GitHub and Gitea/Forgejo allow you to upload files and directories created during a continuous integration run (Artifacts). These can be downloaded as zip files. However there is no simple way to view individual files of an artifact.

That’s why I developed a small web application that allows you to view the artifacts of any CI run in your web browser. This allows you to quickly look at test reports or preview your web projects.

I am hosting a public instance with support for GitHub and Codeberg under https://av.thetadev.de/.

Features

  • 📦 Quickly view CI artifacts in your browser without messing with zip files
  • 📂 File listing for directories without index page
  • 🏠 Every artifact has a unique subdomain to support pages with absolute paths
  • 🌎 Full SPA support with 200.html and 404.html fallback pages
  • 👁️ Viewer for Markdown, syntax-highlighted code and JUnit test reports
  • 🐵 Greasemonkey userscript to automatically add a “View artifact” button to GitHub/Gitea/Forgejo
  • 🦀 Fast and efficient, only extracts files from zip archive if the client does not support gzip
  • 🔗 Automatically creates pull request comments with links to all build artifacts

Examples

Here are some artifacts to try:

SveltePress documentation site: https://cb--thetadev--artifactview--28-2.av.thetadev.de/

A bunch of test files: https://cb--thetadev--artifactview--28-1.av.thetadev.de/

Artifactview’s own test report: https://cb--thetadev--artifactview--65-1.av.thetadev.de/junit.xml?viewer=1

Automatically created pull request comment: https://codeberg.org/ThetaDev/artifactview/pulls/2

  • mormund@feddit.de
    link
    fedilink
    arrow-up
    2
    ·
    4 months ago

    Does GitHub support range requests for artifacts? With that you could read the file index without downloading and caching the entire zip

    • ThetaDev@lemm.eeOP
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      4 months ago

      It does (they of course use their Azure Blob storage under the hood). Forgejo however does not (even though it supports it for releases and packages and Golang has this in their standard library).

      I’ll keep the idea in mind.