Use .charm artefacts in individual integraton tests
#639
Labels
enhancement
New feature or request
Comments
|
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-6696.
|
|
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-6697.
|
DnPlas
added a commit
that referenced
this issue
Dec 17, 2024
This commit enables the "--charm-path" option to pass .charm artefacts to be deployed and tested at an individual level. This change enables the option to pass pre-built charms to the tests to avoid building them on the same test. It also ensures compatibility with the build_charm.py reusable workflow (from canonical/data-platform-workflows). Fixes: #639
DnPlas
added a commit
that referenced
this issue
Dec 17, 2024
This commit enables the "--charm-path" option to pass .charm artefacts to be deployed and tested at an individual level. This change enables the option to pass pre-built charms to the tests to avoid building them on the same test. It also ensures compatibility with the build_charm.py reusable workflow (from canonical/data-platform-workflows). Fixes: #639
DnPlas
added a commit
that referenced
this issue
Dec 17, 2024
This commit enables the "--charm-path" option to pass .charm artefacts to be deployed and tested at an individual level. This change enables the option to pass pre-built charms to the tests to avoid building them on the same test. It also ensures compatibility with the build_charm.py reusable workflow (from canonical/data-platform-workflows). Fixes: #639
DnPlas
added a commit
that referenced
this issue
Dec 17, 2024
This commit enables the "--charm-path" option to pass .charm artefacts to be deployed and tested at an individual level. This change enables the option to pass pre-built charms to the tests to avoid building them on the same test. It also ensures compatibility with the build_charm.py reusable workflow (from canonical/data-platform-workflows). Fixes: #639
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context
Based on the changes proposed in #635 and canonical/bundle-kubeflow#1070, and assuming the changes introduced by canonical/charmed-kubeflow-workflows#88, the individual integration tests must:
charmartefacts generated by theget_charms_build_with_cache.yamlreusable workflow and use them for deploying them and run tests on topWhat needs to get done
integrationjob to download thecharmartefactscharmartefacts for deploying charms under testDefinition of Done
Individual integration tests use
charmartefacts to deploy and test them.The text was updated successfully, but these errors were encountered: