-
Notifications
You must be signed in to change notification settings - Fork 60
project: use pebble snap instead of building #177
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
Conversation
d4b5275 to
c17cef9
Compare
|
The spread failure is due to this bug: https://bugs.launchpad.net/snapd/+bug/2002835 |
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 presume we've got a reminder somewhere to change this to a more stable pebble snap once it's released to a channel other than edge
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, thanks
Now that pebble has been published as a snap we can use it directly instead of building the binary each time. Prime only the binary and "organize" it as /usr/bin/pebble just like the previous part did.
5932a05 to
26ff522
Compare
|
Out of curiosity, what is the speed improvement here? |
|
@sergiusens I compared the spread runs with and without this change and it looks like we went from around ~32min to around ~26min (total). Pretty nice actually |
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Now that pebble has been published as a snap we can use it directly instead of building the binary each time. Prime only the binary and "organize" it as /usr/bin/pebble just like the previous part did.
(CRAFT-1566)