Releases: elabit/robotmk
Releases · elabit/robotmk
Release v1.3.0
Added
- Bakery/Check Plugin: Introduced
completeas new re-execution mode for suites (#206). This is useful for suites that must always run completely because the tests depend on each other. Thus, a suite OK result is returned not when each test was OK in an arbitrary iteration, but rather in a common iteration.
Changed
- Bakery: Introduced "incremental" as a name for the previous re-execution mode.
⚠️ Your existing rules are compatible with that new naming scheme - but they are only saved in the new format after they have been opened and saved (even if there are no changes).
Release v1.2.10-beta-1
Added
- Documentation: Added FAQs with design decisions
- Check: Added the possibility to temporarily skip the execution of suites by placing a
DISABLED(case sensitive) file in the suite's root folder. (#192)
Robotmk will silently ignore this suite as long the DISABLED file is there.
(Thanks Marcus for this suggestion - this is the perfect alternative to commenting out the suite inrobotmk.ymlmanually).
You can also optionally write a reason ("Need a short break.") into the file; it will get logged in Robotmk's log:
2022-08-02 22:25:28,449 RMKrunner [48887] INFO: ####################
2022-08-02 22:25:28,575 RMKrunner [48887] INFO: => Suites to start: sleep
2022-08-02 22:25:28,583 RMKrunner [48887] INFO: ~~~~ Suite ID: sleep ~~~~
2022-08-02 22:25:28,591 RMKrunner [48887] WARNING: Suite 'sleep' is skipped because of the 'DISABLED' flagfile in its suite folder. Reason: Need a short break.
2022-08-02 22:25:28,591 RMKrunner [48887] WARNING: (Be aware that the services in Checkmk will become stale soon.)
2022-08-02 22:25:28,595 RMKrunner [48887] INFO: ... Quitting Runner, bye. ---
Changed
- Bakery rule: Lowered the log retention threshold (#172)
- Check: Fixed a bug which lead to metric names without specials chars like umlauts => metric names can slightly change, sorry. (#197)
Fixed
- Bakery (V2): Added missing
timeoutto async robotmk execution.timeoutis now
set to 5 sec less than the execution interval so that the agent can kill the runner
before the next execution. (#203) - Check: Creates host dir for HTML logs; updated inline help for HTML log icons (#201)
- Check: Allow only 1 runtime threshold by setting the other one to 0 (#198)
Removed
Deprecated
Release v1.2.10-beta
Added
- Documentation: Added FAQs with design decisions
- Check: Added the possibility to temporarily skip the execution of suites by placing a
DISABLED(case sensitive) file in the suite's root folder. (#192)
Robotmk will silently ignore this suite as long the DISABLED file is there.
(Thanks Marcus for this suggestion - this is the perfect alternative to commenting out the suite inrobotmk.ymlmanually).
You can also optionally write a reason ("Need a short break.") into the file; it will get logged in Robotmk's log:
2022-08-02 22:25:28,449 RMKrunner [48887] INFO: ####################
2022-08-02 22:25:28,575 RMKrunner [48887] INFO: => Suites to start: sleep
2022-08-02 22:25:28,583 RMKrunner [48887] INFO: ~~~~ Suite ID: sleep ~~~~
2022-08-02 22:25:28,591 RMKrunner [48887] WARNING: Suite 'sleep' is skipped because of the 'DISABLED' flagfile in its suite folder. Reason: Need a short break.
2022-08-02 22:25:28,591 RMKrunner [48887] WARNING: (Be aware that the services in Checkmk will become stale soon.)
2022-08-02 22:25:28,595 RMKrunner [48887] INFO: ... Quitting Runner, bye. ---
Changed
- Bakery rule: Lowered the log retention threshold (#172)
- Check: Fixed a bug which lead to metric names without specials chars like umlauts => metric names can slightly change, sorry. (#197)
Fixed
- Bakery (V2): Added missing
timeoutto async robotmk execution.timeoutis now
set to 5 sec less than the execution interval so that the agent can kill the runner
before the next execution. (#203) - Check: Creates host dir for HTML logs; updated inline help for HTML log icons (#201)
- Check: Allow only 1 runtime threshold by setting the other one to 0 (#198)
Removed
Deprecated
Release v1.2.9
Fixed
- Check: Changed folder for HTML logs from local to var
Release v1.2.8
- Check: Fixed #189 - Critical threshold / value not transferred to perfdata
Release v1.2.7
- Agent plugin: Fixed a bug in failed test re-execution when the output XML files
were not processed in the correct chronological order. (#185)
Release v1.2.6
- Check: performance data are only created for a S/T/K if the RF result is PASS (#177).
Release v1.2.5
- Check: Fixed #178 when the suite ran, but procudes a fatal error.
Release v1.2.4
- Check: Check crashes when the suite never ran. In this case, no XML is present
and no data can be parsed. The corrected behaviour now is to skip the discovery
of suites but to let the "Robotmk" service report that suites are missing results. (#178)
Release v1.2.3
Fixed
- Check: If results are too old, the check now sets the services to stale (= they
keep their state, but appear faded), whereas the Robotmk service turns into
CRITICAL.