Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 7927c6e99b0095b62af88022b1a738359662126b
https://github.com/tribe29/checkmk/commit/7927c6e99b0095b62af88022b1a738359…
Author: Sergey Kipnis <sergey.kipnis(a)tribe29.com>
Date: 2022-01-22 (Sat, 22 Jan 2022)
Changed paths:
A agents/cmk-agent-ctl/cargo_build.cmd
M buildscripts/scripts/lib/windows.groovy
A buildscripts/scripts/windows-agent-cmk-agent-ctl-build.jenkins
Log Message:
-----------
Add possibility to build rust executable on Windows node
- add scripts
- add two targets
TEST: manual testing of commands from script on Windows node
CMK-9411
Change-Id: I0828f2179288bd35d7e6e3b29ee1dbdf13f039ee
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 6c2006dea45378720294307ca77f1534a3027088
https://github.com/tribe29/checkmk/commit/6c2006dea45378720294307ca77f1534a…
Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com>
Date: 2022-01-21 (Fri, 21 Jan 2022)
Changed paths:
M agents/check_mk_agent.aix
M agents/check_mk_agent.freebsd
M agents/check_mk_agent.linux
M agents/check_mk_agent.openwrt
M agents/check_mk_agent.solaris
A tests/agent-unit/test_get_epoch.sh
M tests/agent-unit/test_log_section_time.sh
M tests/agent-unit/test_run_cached.sh
Log Message:
-----------
be more defensive when calling date
Check that 'date +%s' will not return a literal '+%s'.
Thanks to @rawiriblundell, who suggested a more profound
solution.
We only use a small part of it to keep the maintenance effort low.
Change-Id: I849ceba707b7fbe8025ccca99d9060622dbda4ce
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 04b17c05510237047b8e49b41ea2691de93f0986
https://github.com/tribe29/checkmk/commit/04b17c05510237047b8e49b41ea2691de…
Author: Andreas Umbreit <andreas.umbreit(a)tribe29.com>
Date: 2022-01-21 (Fri, 21 Jan 2022)
Changed paths:
A .werks/13134
Log Message:
-----------
13134 FIX custom_files: Place plugins under the right directory on windows
This Werk fixes a regression that got introduced with Checkmk 2.0.0p18.
The changes from Werk #13131 lead to the situation that custom files placed
under <tt>~/var/check_mk/agents/custom/<pkg>/lib/plugins</tt> accidentally
got packaged directly under the Windows agent's installation directory.
Now, they get placed correctly under <tt><install_dir>\plugins</tt>,
as it was the case before the regression.
Change-Id: I3ab7391f3f00f4c72ebbc15ab09f9cc73ea1dc0a
Branch: refs/heads/2.0.0
Home: https://github.com/tribe29/checkmk
Commit: d88de0afc9285fe146826aab8f61cd7d90ef84ad
https://github.com/tribe29/checkmk/commit/d88de0afc9285fe146826aab8f61cd7d9…
Author: Andreas Umbreit <andreas.umbreit(a)tribe29.com>
Date: 2022-01-21 (Fri, 21 Jan 2022)
Changed paths:
A .werks/13134
Log Message:
-----------
13134 FIX custom_files: Place plugins under the right directory on windows
This Werk fixes a regression that got introduced with Checkmk 2.0.0p18.
The changes from Werk #13131 lead to the situation that custom files placed
under <tt>~/var/check_mk/agents/custom/<pkg>/lib/plugins</tt> accidentally
got packaged directly under the Windows agent's installation directory.
Now, they get placed correctly under <tt><install_dir>\plugins</tt>,
as it was the case before the regression.
SUP-9093
Change-Id: I3ab7391f3f00f4c72ebbc15ab09f9cc73ea1dc0a
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: f42a3179b1378cc4a96261506fa85f7745552f9e
https://github.com/tribe29/checkmk/commit/f42a3179b1378cc4a96261506fa85f774…
Author: Pablo Santiago Blum de Aguiar <pablo.blum(a)tribe29.com>
Date: 2022-01-21 (Fri, 21 Jan 2022)
Changed paths:
M tests/unit/cmk/base/plugins/agent_based/test_kube_pod_restarts.py
Log Message:
-----------
test_kube_pod_restarts: Optionally return an empty fixture
The test in question takes advantage of a mutable fixture (a dictionary
in this case) to assert one aspect of correctness. Basically, it tests
one expected side-effect of the check function.
Relying on a fixture and overriding its object makes resilience tests
fail, as running it once leaves the mutable object in an "invalid"
state for the next iteration.
What makes it an issue is the way with which `pytest-repeat` "tricks"
tests into repeating themselves by adding one additional dimension of
parametrization, which does not trigger a re-assignment of the other
parameters and a consequential reset to their initial states.
To overcome that, the fixture is changed to rely on a flag that tells
whether it should return an empty dict or not. The test can then
override this flag instead of the fixture itself.
Change-Id: I89224cc587dca1ca4d390a3ad32172b99f42eeb8