-
Notifications
You must be signed in to change notification settings - Fork 457
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
docs: add explanation for remote build #4882
Conversation
cf7510b
to
007140f
Compare
Signed-off-by: Callahan Kovacs <callahan.kovacs@canonical.com>
007140f
to
68bcfd3
Compare
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.
Looks good!
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'm going to preemptively approve this because I have to leave for the weekend! I trust you'll do the right thing ;)
Signed-off-by: Callahan Kovacs <callahan.kovacs@canonical.com>
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.
Excellente
Signed-off-by: Callahan Kovacs <callahan.kovacs@canonical.com>
tox run -m lint
?tox run -e test-py310
? (supported versions:py39
,py310
,py311
,py312
)This PR explains how the current and legacy remote builders behave.
The behavior of the new and legacy remote builders is nuanced enough that we need comprehensive documentation before we can comfortably make behavioral changes.
Preview here: https://canonical-snapcraft--4882.com.readthedocs.build/en/4882/explanation/remote-build.html
Fixes #4842
(CRAFT-3000)