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

breaking(build_charms_with_cache.yaml): Remove charms output (JSON string of charms built) #58

Merged
merged 1 commit into from
Jul 28, 2023

Conversation

carlcsaposs-canonical
Copy link
Contributor

Instead of using the JSON string, integration tests should instead download the GitHub artifact and check if a *.charm file exists

If there are multiple *.charm files in a directory, the integration test job should use an input to determine which *.charm file to select (example input: Ubuntu version)

This change makes build_charms_with_cache.yaml more consistent/interchangeable with build_charm_without_cache.yaml

@carlcsaposs-canonical
Copy link
Contributor Author

Example implementation (planning to move to reusable pytest plugin): canonical/mysql-k8s-operator#261

Copy link

@taurus-forever taurus-forever left a comment

Choose a reason for hiding this comment

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

LGTM in general. You are driving our CI.
I suspect we will have TODO here after adding ARM charms... but it is 2024+
LGTM for now. I like cleaner CI API!

P.S. I didn't set Approve to avoid merging by mistake.

Copy link

@taurus-forever taurus-forever left a comment

Choose a reason for hiding this comment

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

LGTM.
JFMI, it is ready for merging?

…string of charms built)

Instead of using the JSON string, integration tests should instead download the GitHub artifact and check if a *.charm file exists

If there are multiple *.charm files in a directory, the integration test job should use an input to determine which *.charm file to select (example input: Ubuntu version)

This change makes build_charms_with_cache.yaml more consistent/interchangeable with build_charm_without_cache_yaml
@carlcsaposs-canonical carlcsaposs-canonical merged commit 557fea4 into main Jul 28, 2023
1 check passed
@carlcsaposs-canonical carlcsaposs-canonical deleted the remove-charms-built-output branch July 28, 2023 11:24
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.

3 participants