Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.core beat.core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.corebeat.core
  • Issues
  • #11
Closed
Open
Issue created Aug 28, 2014 by André Anjos@andre.anjos💬Owner

(Local) Paced development

When the user develops a bit toolchain, s/he cannot test the toolchain if algorithms for all blocks are not implemented. This makes development a bit hard and demotivating.

A simple solution to this problem would be to implement some sort of "noop" algorithm that could live inside the "beat" user account.

In local execution mode (with beat run), if such an algorithm would be found, then it would not execute the current algorithm or any other following it. This would allow the user to place "beat/noop" as an algorithm in all blocks to be developed and focus on a single block at a time.

Assignee
Assign to
Time tracking