News

Parallel starting / stopping of components

Added by R. Haschke about 2 years ago

Previous approach didn't allow for truly parallel starting of components.
Also, the level order was not considered when manually starting several groups in parallel.
The new fully event-based scheme, should resolve those issues. Please report any open issues.

Attention: The remark from previous change still holds true:
Before, components were started in given order, -w option specifying to wait for a component before proceeding to the next.
Now, all components on the same level are started in parallel. -w option simply states the timeout period, before we give up to wait for this component to be ready.

New branch 0.5

Added by R. Haschke about 4 years ago

  • allow for parallel starting / stopping of components at same level
    different levels are handled consecutively
  • even different groups can be started / stopped in parallel
  • individual components start / stop in between too
  • start / stop within same group conflicts with each other -> cancel a running command
  • gui feedback on group commands
  • removed level command buttons
  • removed obsolete -c option: components are checked in 1s intervals at most
    time required for checking, adds on top of this
  • option -w defaults to 5s (timeout for successful component start)

If you observe strange start order, check your levels!
Before, components were started in given order, -w option specifying to wait for a component before proceeding to the next.
Now, all components on the same level are started in parallel. -w option simply states the timeout period, before we give up to wait for this component to be ready.

New branch 0.4 created

Added by N. Köster over 4 years ago

We released a new version branch "0.4" and added a version tag called "v0.4.0".

Besides multiple bugfixes, we added a new feature: Organizing components using tabs! This is especially helpful when dealing with multiple components of various types. See the wiki for details.

New branch 0.3 created

Added by J. Wienke over 5 years ago

Since we are planning to incorporate some new features in the master version, we have created a 0.3 branch to freeze the current state and master has been pushed to 0.4.

(1-4/4)

Also available in: Atom