RFC: Deployer tooling

[julianschuler]

Please add all your deployer tooling improvement ideas to this issue thread.

See #1479 for the initial issue.

[oleflb]

The way I see this, the problem can be divided into different stages:

• Pregame

  • A better way to communicate branches (idea: telegram bot)
  • A better way to communicate jersey number assignments (idea: telegram bot as well)

• During Game

  • Keep Track of robot substitutions
  • Keep track of code and parameter changes

• Post game

  • Common game branch naming scheme
  • Upload all replay data to a fixed location
  • Ideally the replay data should be self-describing, i.e. some reference to the code (currently we have the folder names for that)
  • probably out of scope for deployer tooling
    • automatic hulk_imagine application to all uploaded replay data for Long-term data preservation
    • some sort of web-based browser for replay data, allowing to quickly replay specific players from different matches

[schmidma]

Agreeing to ole, adding some additional ideas (also beyond the deployer role):

• Pregame
  • communicating the status (not continuously asking "what is the current state, are you deploying, etc")
  • tooling in this phase can also be designing a process or communication strategies
• During Game
  • central logging, all HULKs can add ideas, or observations to the log; probably requires a special agreed on format (e.g. timestamp, robot, kind of observation, etc...)
  • using the team communication monitor logs? (the only advantage: may be showing opponent robots)
• Post Game
  • status of postgame progress
  • idea on code reference: shipping a source distribution with an upload