Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support helm.sh/hook: test-success/failure #2038

Closed
alexec opened this issue Jul 26, 2019 · 2 comments
Closed

Support helm.sh/hook: test-success/failure #2038

alexec opened this issue Jul 26, 2019 · 2 comments
Labels
enhancement New feature or request wontfix This will not be worked on

Comments

@alexec
Copy link
Contributor

alexec commented Jul 26, 2019

See #355.
@alexec alexec added enhancement New feature or request helm labels Jul 26, 2019
@alexec alexec changed the title Support helm.sh/hook: test-success Support helm.sh/hook: test-success/failure Jul 26, 2019
@alexec alexec mentioned this issue Jul 26, 2019
Closed
@jessesuen
Copy link
Member

jessesuen commented Jul 29, 2019 •
edited
Loading

Helm test hooks are only used through a helm test command. I don't think we have use for this and would recommend closing this as wontfix.

@alexec alexec added the wontfix This will not be worked on label Jul 29, 2019
@alexec alexec closed this as completed Jul 29, 2019
@NotAndD
Copy link

NotAndD commented Jun 4, 2021

But what if I want to exec a manual test after I applied the Chart / I updated something and sync the application? I think it would be pretty useful if argo-cd supported starting a test hook manually from its interface.

I know that helm test is not that used, but it's a way to execute manual Jobs only when needed and under the supervision of who starts them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request wontfix This will not be worked on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@alexec @jessesuen @NotAndD