Branch: refs/heads/2.1.0
Home: https://github.com/tribe29/checkmk
Commit: 17449786ba11fcc12e2b78bbaefac68716c98c8b
https://github.com/tribe29/checkmk/commit/17449786ba11fcc12e2b78bbaefac6871…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2022-07-25 (Mon, 25 Jul 2022)
Changed paths:
M tests/composition/conftest.py
Log Message:
-----------
Fix composition tests: git command exited with 128
Since an update of the git command in the Ubuntu 21.10 build image,
the composition tests failed because of some tightened security checks
in git. The git command failed with this error:
```
root@fabef7565f8d:/home/jenkins/workspace/cmk_200/test-composition# git status
fatal: detected dubious ownership in repository at '/home/jenkins/workspace/cmk_200/test-composition'
To add an exception for this directory, call:
git config --global --add safe.directory /home/jenkins/workspace/cmk_200/test-composition
root@fabef7565f8d:/home/jenkins/workspace/cmk_200/test-composition# echo $?
128
```
Even if we could fix the issue in some way, we apply this change
instead. It skips the needless execution of the git command in case the
BRANCH variable was set. Previous to this change the git command was
executed even when the BRANCH environment variable was set, just to
compute the default value we don't need in this case.
Change-Id: I4ec6c2393575b7f4e8494f8d80a4c918d01a4603
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: c4b0263881d8d9b3f348ba06be23a8392027edec
https://github.com/tribe29/checkmk/commit/c4b0263881d8d9b3f348ba06be23a8392…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2022-07-25 (Mon, 25 Jul 2022)
Changed paths:
M tests/composition/conftest.py
Log Message:
-----------
Fix composition tests: git command exited with 128
Since an update of the git command in the Ubuntu 21.10 build image,
the composition tests failed because of some tightened security checks
in git. The git command failed with this error:
```
root@fabef7565f8d:/home/jenkins/workspace/cmk_200/test-composition# git status
fatal: detected dubious ownership in repository at '/home/jenkins/workspace/cmk_200/test-composition'
To add an exception for this directory, call:
git config --global --add safe.directory /home/jenkins/workspace/cmk_200/test-composition
root@fabef7565f8d:/home/jenkins/workspace/cmk_200/test-composition# echo $?
128
```
Even if we could fix the issue in some way, we apply this change
instead. It skips the needless execution of the git command in case the
BRANCH variable was set. Previous to this change the git command was
executed even when the BRANCH environment variable was set, just to
compute the default value we don't need in this case.
Change-Id: I4ec6c2393575b7f4e8494f8d80a4c918d01a4603
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 2eabf2e2b156a45d103c7dc09a1650370dc106a4
https://github.com/tribe29/checkmk/commit/2eabf2e2b156a45d103c7dc09a1650370…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2022-07-25 (Mon, 25 Jul 2022)
Changed paths:
M cmk/gui/wato/pages/rulesets.py
Log Message:
-----------
Fix GUI crawl: Make feature toggle explicit
The listing of rules on the rule set page has an optional feature:
Analyse matching of the rules, visualized by the colored circles). This
mode was previously enabled once the `self._hostname` was set. However,
during the recent changes this was confused multiple times which seems
to be a good sign that we have to clean this up somehow.
Now this change tries to make it clearer by making the feature toggle
more explicit.
Change-Id: I5a82cb046b02e6b58d74dd259dfd13ac6b34a42d
Branch: refs/heads/2.0.0
Home: https://github.com/tribe29/checkmk
Commit: 858e450ce07b6b24e5aab339138fe6bb7fff27a5
https://github.com/tribe29/checkmk/commit/858e450ce07b6b24e5aab339138fe6bb7…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2022-07-25 (Mon, 25 Jul 2022)
Changed paths:
M tests/composition/conftest.py
Log Message:
-----------
Fix composition tests: git command exited with 128
Since an update of the git command in the Ubuntu 21.10 build image,
the composition tests failed because of some tightened security checks
in git. The git command failed with this error:
```
root@fabef7565f8d:/home/jenkins/workspace/cmk_200/test-composition# git status
fatal: detected dubious ownership in repository at '/home/jenkins/workspace/cmk_200/test-composition'
To add an exception for this directory, call:
git config --global --add safe.directory /home/jenkins/workspace/cmk_200/test-composition
root@fabef7565f8d:/home/jenkins/workspace/cmk_200/test-composition# echo $?
128
```
Even if we could fix the issue in some way, we apply this change
instead. It skips the needless execution of the git command in case the
BRANCH variable was set. Previous to this change the git command was
executed even when the BRANCH environment variable was set, just to
compute the default value we don't need in this case.
Change-Id: I4ec6c2393575b7f4e8494f8d80a4c918d01a4603
Branch: refs/heads/2.1.0
Home: https://github.com/tribe29/checkmk
Commit: 5b012fa185580ed8ac362bec8d920259eb756d69
https://github.com/tribe29/checkmk/commit/5b012fa185580ed8ac362bec8d920259e…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2022-07-25 (Mon, 25 Jul 2022)
Changed paths:
M cmk/gui/wato/pages/rulesets.py
Log Message:
-----------
Fix GUI crawl: Make feature toggle explicit
The listing of rules on the rule set page has an optional feature:
Analyse matching of the rules, visualized by the colored circles). This
mode was previously enabled once the `self._hostname` was set. However,
during the recent changes this was confused multiple times which seems
to be a good sign that we have to clean this up somehow.
Now this change tries to make it clearer by making the feature toggle
more explicit.
Change-Id: I5a82cb046b02e6b58d74dd259dfd13ac6b34a42d