-
Notifications
You must be signed in to change notification settings - Fork 220
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
v3.9.0 fails on linting (v3.8.0 still works) #580
Comments
The issue seems to be related to: #552. Since it is passing down the |
Perhaps we should have more than one helm-extra-args, ie: helm-install-extra-args, helm-upgrade-extra-args, helm-lint-extra-args, etc. Same as above, ct 3.9.0 now breaks because What do you think, @AndersBennedsgaard |
Which was also suggested in #540 |
@joejulian I agree, that sounds like a good solution going forward, but we should probably keep the P.s. I haven't actually had issues with 3.9.0 yet, so you only just made me aware of this (sorry for the inconveniences my change has brought 😞 ) |
TLDR :Same issue Have Time To Read :my use caseGoal:Trigger chart linting on merge request in gitlab. Problem :Won't read dynamic branch naming.
#!/bin/bash
changed=$(ct list-changed --target-branch ${CI_MERGE_REQUEST_TARGET_BRANCH_NAME})
if [[ -n "$changed" ]]; then
echo 'Something changed'
ct lint --target-branch ${CI_MERGE_REQUEST_TARGET_BRANCH_NAME} --validate-maintainers=false
fi
|
this looks like a duplicate of #577 , so I suggest the same workaround for gitlab-ci : before_script:
- git branch "$target_branch" "origin/$target_branch" |
released https://github.com/helm/chart-testing/releases/tag/v3.10.0 this should be fixed |
@joejulian @AndersBennedsgaard I am facing same issue. Fails in |
We're running off my fork for now. See our workflows in github.com/redpanda-data/helm-charts. |
there is a fix for that #605 |
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
Version of Helm and Kubernetes:
What happened:
https://github.com/spiffe/helm-charts/actions/runs/5602051333/jobs/10246787989?pr=324#step:6:20
What you expected to happen:
To have the pipeline succeed just like it does with the v3.8.0 version of
ct
.How to reproduce it (as minimally and precisely as possible):
fetch: 0
ct lint --config ct.yaml --target-branch $(TARGET_BRANCH) --check-version-increment=false
Anything else we need to know:
See here the working variant with v3.8.0
The text was updated successfully, but these errors were encountered: