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: Use charmcraftcache for builds instead of GitHub Actions cache #115

Merged
merged 2 commits into from
Jan 8, 2024

Conversation

carlcsaposs-canonical
Copy link
Contributor

@carlcsaposs-canonical carlcsaposs-canonical commented Jan 4, 2024

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

Example migration for breaking changes: canonical/mysql-router-k8s-operator@8f30968

…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
@carlcsaposs-canonical
Copy link
Contributor Author

carlcsaposs-canonical commented Jan 4, 2024

Tested on canonical/mysql-router-k8s-operator#180

@carlcsaposs-canonical
Copy link
Contributor Author

Synchronize merge with canonical/charmcraftcache-hub#29

Copy link
Contributor

@dragomirp dragomirp left a comment

Choose a reason for hiding this comment

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

LGTM

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.

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.

@carlcsaposs-canonical
Copy link
Contributor Author

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 build

Also I don't think it will help with backwards compatibility—I only think it will make things fail silently

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.

None yet

3 participants