-
Notifications
You must be signed in to change notification settings - Fork 11
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: Use charmcraftcache
for builds instead of GitHub Actions cache
#115
Conversation
…cache Breaking changes for charms with "pack-wrapper" environment in tox.ini: - tox environment "pack-wrapper" renamed to "build-wrapper" - tox environment "build" renamed to "build-production" - new tox environment "build-dev" for cached builds
Tested on canonical/mysql-router-k8s-operator#180 |
Synchronize merge with canonical/charmcraftcache-hub#29 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would keep tox run -e build
as a production build. It will simplify everything a bit and keep backward compatibility... but it looks like too late here. LGTM as I will not be reachable the next week.
The tox config for that is more complicated (if it's even possible)—unless the non-production build environment name does not contain Also I don't think it will help with backwards compatibility—I only think it will make things fail silently |
Breaking changes for charms with "pack-wrapper" environment in tox.ini:
Example migration for breaking changes: canonical/mysql-router-k8s-operator@8f30968