Branch: refs/heads/2.0.0
Home: https://github.com/tribe29/checkmk
Commit: 2d8bf60ca837993c522f1c77ea61a3de428742fd
https://github.com/tribe29/checkmk/commit/2d8bf60ca837993c522f1c77ea61a3de4…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2021-12-22 (Wed, 22 Dec 2021)
Changed paths:
A .werks/13324
M buildscripts/scripts/build-cmk-version.jenkins
M omd/Makefile
Log Message:
-----------
13324 SEC Shipping software bill of materials with Checkmk
A software bill of materials can be used to analyze the components that are
part of Checkmk. An accurate inventory of all components enables organizations
to identify risk, allows for greater transparency, and enables rapid impact
analysis.
Checkmk packages are now shipping a BOM in OWASP CycloneDX format. As of
Checkmk 2.1.0 and 2.0.0p18 it can be found in each site at the path
<tt>share/doc/bill-of-materials.json</tt>.
We also publish the BOM to internal dependency track instance.
Change-Id: I6dc73b7accc5eaf237fa9c69828bb7bf11092563
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 3fb76d7fa6f100b9f72323787731444fd6d5cfe7
https://github.com/tribe29/checkmk/commit/3fb76d7fa6f100b9f72323787731444fd…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2021-12-22 (Wed, 22 Dec 2021)
Changed paths:
A .werks/13324
M buildscripts/scripts/build-cmk-version.jenkins
M omd/Makefile
Log Message:
-----------
13324 SEC Shipping software bill of materials with Checkmk
A software bill of materials can be used to analyze the components that are
part of Checkmk. An accurate inventory of all components enables organizations
to identify risk, allows for greater transparency, and enables rapid impact
analysis.
Checkmk packages are now shipping a BOM in OWASP CycloneDX format. As of
Checkmk 2.1.0 and 2.0.0p18 it can be found in each site at the path
<tt>share/doc/bill-of-materials.json</tt>.
We also publish the BOM to internal dependency track instance.
Change-Id: I6dc73b7accc5eaf237fa9c69828bb7bf11092563
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: c6b698d16802d0b0e495d12f0299505d0fddb1d4
https://github.com/tribe29/checkmk/commit/c6b698d16802d0b0e495d12f0299505d0…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2021-12-22 (Wed, 22 Dec 2021)
Changed paths:
M tests/unit/test_pipfile.py
Log Message:
-----------
Add test to ensure the Pipfile.lock is in sync with Pipfile
We now had an outdated Pipfile.lock multiple times which then
resulted in the version build jobs recognizing this issue with
the message:
```
Pipfile.lock (f9092b) out of date, updating to (cdb517)...
```
Which then failed because the build job is not using the `--pre` flag
which we currently use for building our Pipfile.lock because black is
only releasing preview releases. Anyway. Even if that would work, then
we don't want to create a new lock during the version builds.
Now, to detect this as early as possible, there is this test.
Change-Id: I85e2732ae8799b90025dce26aac934d381c7b7a6
Commit: 7df128e91a6120e9cc0f5012f691d49da2b4244d
https://github.com/tribe29/checkmk/commit/7df128e91a6120e9cc0f5012f691d49da…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2021-12-22 (Wed, 22 Dec 2021)
Changed paths:
M Pipfile.lock
Log Message:
-----------
Regenerate Pipfile.lock
Change-Id: I9c75c1dfb4e85c8cac968c2571dcbf1d703c2e9d
Compare: https://github.com/tribe29/checkmk/compare/bdaae5e7a7e5...7df128e91a61
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 915fcbfc1a7d753e71197a43197ea4e123999b03
https://github.com/tribe29/checkmk/commit/915fcbfc1a7d753e71197a43197ea4e12…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2021-12-21 (Tue, 21 Dec 2021)
Changed paths:
M Pipfile.lock
Log Message:
-----------
Revert "Regenerated Pipfile.lock."
The setuptools update from 59.6.0 to 60.0.3 may be the problem.
Have not looked at this in detail yet.
This reverts commit 13649ea897bfcb9b8e02a7d3426a4b078cbc517d.
Branch: refs/heads/2.0.0
Home: https://github.com/tribe29/checkmk
Commit: 09f2318cf0525a03cb0057bcb54cd2612ec69f00
https://github.com/tribe29/checkmk/commit/09f2318cf0525a03cb0057bcb54cd2612…
Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com>
Date: 2021-12-21 (Tue, 21 Dec 2021)
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.solaris
Log Message:
-----------
Allow custom caching prefixes in local checks
THIS IT MAY CHANGE AT ANY TIME
Cached local checks can now include their custom prefix in
the `cached(${CACHED_AT},${VALID_FOR})` format.
This allows for various workarounds for problems caused by
the fact that the validitiy period and the data generation
interval are always the same, which leads to periodically
occurring moments without valid data.
This is only an intermediate solution, until we find a
proper way of addressing this. You must not rely on this
behaviour, which is why there won't be a werk for this.
Change-Id: I4df7a242137364de53ddf7272ecb9f7dc5eed927
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: e6a361f4a4d9b0e6f0f8e87f60166243beec30bb
https://github.com/tribe29/checkmk/commit/e6a361f4a4d9b0e6f0f8e87f60166243b…
Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com>
Date: 2021-12-21 (Tue, 21 Dec 2021)
Changed paths:
M tests/agent-unit/test_run_cached.sh
Log Message:
-----------
cleanup tests
Change-Id: I588fe325764a5c20d9861ff41781ce6e73145fca
Commit: 0f17a6984c15bee0e62d0dfa63ef7f63cd8d34d3
https://github.com/tribe29/checkmk/commit/0f17a6984c15bee0e62d0dfa63ef7f63c…
Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com>
Date: 2021-12-21 (Tue, 21 Dec 2021)
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
M tests/agent-unit/test_run_cached.sh
Log Message:
-----------
Allow custom caching prefixes in local checks
Cached local checks can now include their custom prefix in
the `cached(${CACHED_AT},${VALID_FOR})` format.
This allows for various workarounds for problems caused by
the fact that the validitiy period and the data generation
interval are always the same, which leads to periodically
occurring moments without valid data.
This is only an intermediate solution, until we find a
proper way of addressing this. You must not rely on this
behaviour, which is why there won't be a werk for this.
Change-Id: I4df7a242137364de53ddf7272ecb9f7dc5eed927
Compare: https://github.com/tribe29/checkmk/compare/ea1ee9355d7b...0f17a6984c15