v2.0.0-alpha-5

This is a test build not intended for public use.

Changes

• Replace most spinlocks with asynchronous tokio functionality.
• Replace clokwerk with asynchronous tokio tasks.
• Simplify suite results data model.

v2.0.0-alpha-4

This is a test build not intended for public use.

Changes

• Improved error handling for missing sessions.
• Support for RCC profile, handled during RCC setup.

v2.0.0-alpha-3

This is a test build not intended for public use.

Changes

• Rename suite name --> suite ID.

v2.0.0-alpha-2

This is a test build not intended for public use.

Changes

• Activate RCC long path support during setup.

v2.0.0-alpha-1

This is a test build not intended for public use.

Changes

• Fixed a bug in reporting the current scheduler phase.

v2.0.0-alpha

This is a test build not intended for public use.

Release v1.4.2

Compatibility release for Checkmk V2.2

Changed

• Changed location of bakery script (#234)

Release v1.4.1

⚠️ This version is not compatible with Checkmk 2.2

Fixed

• agent plugin: fixed bug when piggyback was set, runner crashed

Release v1.4.0

Changed

• The Robotmk mechanism behind the RF parameter --exitonfailure has been optimized and clearly documented in the inline help. If this option was set, the remaining tests that were not executed were previously marked as FAIL or CRITICAL. This is the default in Robot Framework (see RF user guide), but in Checkmk it lead to an alarm not only for the root cause (the failed test), but also for the subsequent errors.
  The behavior of Robotmk has been slightly modified in that the tests omitted due to a previous failure are filtered out and not passed to Checkmk for evaluation anymore. Tests that have not been executed become "stale", and false alarms are thus avoided. (Thanks for the valuable feedback.)

Release v1.3.1

Fixed

• robotmk-runner.py crashed when no re-execution strategy was set at all (closes #209)