8000 Support fail-at-end mode for ct lint to test all custom values files · Issue #738 · helm/chart-testing · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Support fail-at-end mode for ct lint to test all custom values files #738

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
shmuelarditi opened this issue May 6, 2025 · 0 comments
Open

Comments

@shmuelarditi
Copy link
shmuelarditi commented May 6, 2025

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.

Image

Image
-- After fixing dev it moved to prod --
Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant
0