-
Notifications
You must be signed in to change notification settings - Fork 12
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
feat: use platform name in build instance name #601
Conversation
ed273d0
to
2d776a3
Compare
Integration test failure looks unrelated, something is going on with launchpad. https://api.staging.launchpad.net/devel/people/+me isn't responding |
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.
Excellent
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.
Nice, thanks!
4d20752
to
d93c378
Compare
forced push to bump craft-providers and prep for a rebase |
d93c378
to
7e165b1
Compare
blocked by #603 |
Signed-off-by: Callahan Kovacs <callahan.kovacs@canonical.com>
This ensures each platform is built in its own build environment. Signed-off-by: Callahan Kovacs <callahan.kovacs@canonical.com>
7e165b1
to
ca8a159
Compare
force-pushing to update date in changelog and prep for rebase |
tox
?Changes the build instance name to use the platform rather than the
build-on
andbuild-for
architectures.This prevents the same build environment being used for multiple platforms. See canonical/charmcraft#2069 for examples.
Fixes #600
Unblocks canonical/charmcraft#2069
(CRAFT-3859)