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.

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

Use single (cached) build for integration tests & release #655

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

carlcsaposs-canonical
Copy link

Created as example per request of @NohaIhab

DnPlas and others added 3 commits January 17, 2025 12:15
)

* ci, tests: pass charm artefacts to deploy and test charms

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: canonical#639

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Renamed from release.yaml

Comment on lines +24 to +25
# TODO: use canonical/charming-actions/promote-charm?
uses: canonical/charming-actions/[email protected]

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

promote-charm looks like a new action that might work better here? not sure

Comment on lines +10 to +14
destination_channel:
description: CharmHub channel to publish to
required: false
default: 'latest/edge'
type: string

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this input ever used? I would imagine you would just dispatch the workflow on the correct branch and then the charming-actions/channel would get the channel right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants