Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
beat.cmdline
beat.cmdline
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 22
    • Issues 22
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • beat
  • beat.cmdlinebeat.cmdline
  • Issues
  • #62

Closed
Open
Opened Sep 05, 2019 by Samuel GAIST@samuel.gaist
  • Report abuse
  • New issue
Report abuse New issue

Add support for remote experiments execution handling

Currently, beat/beat.cmdline> only offers to run experiment locally.

This issue tracks the implementation of the commands needed to start, cancel and monitor a remote experiment.

The current monitoring implementation in beat/beat.web> is based on a 5 second timer which, on timeout, will fetch the running experiment and, based on the content returned, update the information panel and toolchain representation.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
1
Labels
enhancement
Assign labels
  • View project labels
Reference: beat/beat.cmdline#62