Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • heptapod heptapod
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 161
    • Issues 161
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • heptapod
  • heptapodheptapod
  • Issues
  • #339

Closed
Open
Created Sep 03, 2020 by Georges Racinet@gracinet🦑Owner

Tarballs generation for the Rails app

Pushing tarballs for this project to a permanent download site will be a step for omnibus-heptapod#1 (closed) (hence #338 (closed)).

It is also probably useful for source installations: don't need to install an arbitrary version of Mercurial before the exact specification is available and various downstream packaging efforts.

Of course we'd like to do this in a CI job, using hg archive and running automatically for Heptapod tags. Because we want to be able to push intermediate testing Docker images, we also need to produce tarballs for arbitrary revisions, perhaps with a manual job.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking