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

La mise à jour du service Gitlab est terminée. Merci aux collègues du service de production de la DSI qui ont réalisé cette opération qui outre les aspects évolution du logiciel nous a permis de faire le nécessaire face à des failles de sécurité.
Les principales releases notes concernant cette montée de version sont disponibles ici :
https://about.gitlab.com/releases/2023/01/22/gitlab-15-8-released/
https://about.gitlab.com/releases/2022/12/22/gitlab-15-7-released/
https://about.gitlab.com/releases/2022/11/22/gitlab-15-6-released/

  • vidjilvidjil
  • vidjilvidjil
  • Issues
  • #4261
Closed
Open
Issue created Apr 23, 2020 by Mikaël Salson@mikael-sOwner

Upgrade issue with classification

@meidanis points out that his upgrade failed following !627 (merged):

Hi Guys! That's great! You created a field to allow administrators to sort the analysis configs in a custom order, instead of alphabetical order. At least that's what I understood with my so-so- French reading the comment to merge request !627 (merged) (merged).

This, however, posed a problem for me. My database doesn't have this field. So, I guess I'll have to do the procedure under "Migrating data" in the documentation, re-create a Vidjil installation from scratch, and, when I load back my database, the field will be there, and the vidjil_utils.py script will take care of initializing the classification field.

Is that it? I'll be glad to do it. Just confirm that this is indeed the process. And I guess I will have to do that every time the database changes.

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