Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
vidjil
vidjil
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,688
    • Issues 1,688
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 84
    • Merge Requests 84
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • vidjil
  • vidjilvidjil
  • Issues
  • #3300

Closed
Open
Opened Jun 18, 2018 by Mathieu Giraud@magiraudOwner

Ordre sur les flags de task.py

Une pensée après #3289 (closed) / !209 (merged) : on aurait pu avoir des flags avec des opérations d'ordre (comme ce qu'on met dans le mail) :

NO_JOB → QUEUED → ASSIGNED → RUNNING → COMPLETED

Mais bon, c'est sûrement inutilement compliqué.

Edited Jun 18, 2018 by Mathieu Giraud
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: vidjil/vidjil#3300