Support fail-at-end mode for ct lint to test all custom values files · Issue #738 · helm/chart-testing · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when using ct lint with multiple *-values.yaml files in the ci/ directory of a chart, chart-testing runs them sequentially but stops on the first error. This makes it hard to use ct in CI pipelines as a linter or pre-merge check, because developers get only one error at a time and must repeatedly fix → commit → rerun.
in the bellow screenshots you can see that as part of our linting ci running on PR's, we are taking the existing value files, and renaming them according to the documnetation with -values.yaml suffix, and putting them in the ci directory inside the chart being testedת and it fails on the first custom values file even tho all of them should fail.
i've verified it by fixing the dev values file and then it was able to catch errors in another value file next on the list.
-- After fixing dev it moved to prod --
The text was updated successfully, but these errors were encountered:
Currently, when using ct lint with multiple *-values.yaml files in the ci/ directory of a chart, chart-testing runs them sequentially but stops on the first error. This makes it hard to use ct in CI pipelines as a linter or pre-merge check, because developers get only one error at a time and must repeatedly fix → commit → rerun.
in the bellow screenshots you can see that as part of our linting ci running on PR's, we are taking the existing value files, and renaming them according to the documnetation with -values.yaml suffix, and putting them in the ci directory inside the chart being testedת and it fails on the first custom values file even tho all of them should fail.
i've verified it by fixing the dev values file and then it was able to catch errors in another value file next on the list.
-- After fixing dev it moved to prod --
The text was updated successfully, but these errors were encountered: