Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
T
tails
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 960
    • Issues 960
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 15
    • Merge Requests 15
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #12127

Closed
Open
Created Jan 10, 2017 by sajolida@sajolidaMaintainer

Make "notes" more structured in the description of our mirror pool

Originally created by @sajolida on #12127 (Redmine)

So we’ve been using the “notes” field in our JSON schema for at least two different things very recurrently:

  • URL of stats (8 times right now), so maybe having a dedicated “stats”
    string would be cool.
  • Failures, with a date and a description. Most of the time we
    only keep the latest failure. Sometimes we keep two (see
    https://tails.unixcorn.org/tails/). So maybe this deserves a
    dedicated field as well. It could be a string called “disabled_because”.

Having these two out of the way would tidy up most of the things.

I want to try to implement this and learn a bit of JSON on the way.

Related issues

  • Related to #14922 (closed)
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None