[checkmk-commits] [tribe29/checkmk] c6b698: Add test to ensure the Pipfile.lock is in sync wit...

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