Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • F flyspray2gitlab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Kevin Morris
  • flyspray2gitlab
  • Issues
  • #24
Closed
Open
Created Apr 03, 2021 by Kevin Morris@kevrOwner

Improve rollback

Rollback is pretty nice right now, however, it does not handle the case well where a user CTRL+C's randomly during import -- we can lose the task being imported if the exception throws before we track it.

Part of the issue here is that the import function is quite gigantic and complex. We should really review that thing and split it up into manageable pieces; at that point, we could more easily define exception paths and rollback more clearly.

Also, with a bit more hacking, this could be done without a rework. That is not an excuse to avoid decoupling it.

Edited Apr 03, 2021 by Kevin Morris
Assignee
Assign to
Time tracking