-
Notifications
You must be signed in to change notification settings - Fork 57
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
Helm deployment issue with custom chartDir option #1038
Labels
bug
Something isn't working
Comments
serverhorror
added a commit
to serverhorror/ods-jenkins-shared-library
that referenced
this issue
Oct 19, 2023
This will bail out if the repository is ambigious about the deployment descriptor. It will fail if: * there is no deployment descriptor * there is more than one deployment descriptor For a successfull release to happen, developers are required to "clean" their repository of unrelated deployment desciptors that could interfere with the current version.
serverhorror
added a commit
to serverhorror/ods-jenkins-shared-library
that referenced
this issue
Oct 19, 2023
This will bail out if the repository is ambigious about the deployment descriptor. It will fail if: * there is no deployment descriptor * there is more than one deployment descriptor For a successfull release to happen, developers are required to "clean" their repository of unrelated deployment desciptors that could interfere with the current version.
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
One of the available customizations for Helm deployments is to specify the path where you have the Charts. This feature works fine but if you have your charts not in a folder on the root of your repository but in a subfolder inside it once you start a release with orchestration pipeline it will fail to find the DeploymentDescriptor.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Pipeline should deploy Helm chart successfully regardless of the path it is stored so long and it is configured using available customization options.
Screenshots
Affected version:
Log Output
Aditional notes:
The issue is comming from this part of the code: https://github.com/opendevstack/ods-jenkins-shared-library/blob/master/src/org/ods/orchestration/phases/DeployOdsComponent.groovy#L131-L140
The text was updated successfully, but these errors were encountered: