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

Si vous êtes un personnel Inria et que vous souhaitez participer aux tests de notre future plateforme Gitlab basée sur la version ultimate avec gitlab LFS activé merci de contacter Didier Chassignol.

  • allgo
  • allgoallgo
  • Issues
  • #217
Closed
Open
Created Jul 04, 2018 by BAIRE Anthony@abaireOwner

include the WebappVersion.id in docker image tags

The docker images names are formatted as: <Webapp.docker_name>:<WebappVersion.number>. This is the name of the docker image as it is stored in the registry and as it is presented to the user.

This proposal is to:

  • keep the same name presented to the user (<Webapp.docker_name>:<WebappVersion.number>)
  • but store them internally as <Webapp.docker_name>:<WebappVersion.number>-id<WebappVersion.id> (with the WebappVersion.id appended)

There are multiple reasons to do that:

  • this will simplify the controller, because it will no longer be necessary to track the exact state of images (when pushing/pulling from the registry) when the user updates a version (because it will have a different tag in the registry)
  • this will prevent reusing images from a removed webapp (eg: a user removes a webapp, another user creates a webapp with the same name, we had at least one occurrence of this case)
  • this will make easy to implement image recovery: we can keep removed images in the registry for some time (eg: 1 month) before they are really deleted

This should be done in Q3, because if we do it later, the migration will be tricky.

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