If we have a step that builds the charm under test, we can save that .charm file as an artifact to be re-used across other workflows, reducing errors (timeouts, networking, transitory) and execution time. For instance:
Build and deploy charm for running e2e integration tests -> save .charm file as artifact.
Run observability tests using the charm built in the previous step.
If we have a step that builds the charm under test, we can save that
.charm
file as an artifact to be re-used across other workflows, reducing errors (timeouts, networking, transitory) and execution time. For instance:.charm
file as artifact.