Skip to content

GitLab

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

Closed
Open
Opened Dec 11, 2018 by Joseph Walton-Rivers@webpigeon🖥Owner

Use task queing for multi-host building

At the moment if you run the builder on two machines, it has the potential to klobber the results from one of the runs. There are two parts to this fix:

  1. on the server side implement some form of optimistic locking for score updates
  2. add a task queue for compilation and games to avoid long running tasks being duplicated and one of the results being klobbered.
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: hanabi/build-engine#5