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
snap: refresh snap for base: core22
#1679
Conversation
This is now building here: https://launchpad.net/~saviq/+snap/edge - it failed on s390x and ppc64el due to dependency issues. I will follow up with a rework of the configuration hook to work with a configuration file rather than the environment. |
oh, thanks for doing this. We noticed that it didn't get update for a while. Could you please make sure it doesn't run as root in snap? thanks Could you please add me as maintainer too ? (sylvestre@debian.org is my login - I am doing that as Mozilla upstream) |
About the s390x port, see #1442 |
Yeah, I never dotted all the "i"'s on this…
You've got mail, and we've requested it to get moved to Mozilla: https://forum.snapcraft.io/t/publisher-change-request-for-sccache/34440
ACK. I've added workflows to build the snap, but you'd have to enable actions from |
yeah, I will ask the team to enable it, thanks :) |
Cool, for those to upload to the snap store, you'll need to set the snapcraft export-login --snaps sccache --channels="*edge*" --acls package_access,package_push,package_release - Or drop that part and store as artifacts instead, your call :) Personally I use a bot account for those uploads, so if you have one like that - and want CI to upload to the store - let's add it as a collaborator as well? |
Uploading them on tagged releases works for me |
I've just dropped the daemon altogether. From what I understand about how sccache operates, it doesn't make sense to have a central server. |
I'd say it only makes sense to upload from PRs (that's how it's currently set up), to Builds into other channels should be set up at https://snapcraft.io/sccache/builds, or through Launchpad snap recipes, once we merge this PR (no point before we do) - this will get you more architectures and a more stable build environment than the Actions one. If you have other means of testing, we may well skip publishing the snap from PRs. I'd still build from PRs in case something breaks in there. |
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #1679 +/- ##
==========================================
+ Coverage 29.33% 29.40% +0.07%
==========================================
Files 49 49
Lines 17056 17056
Branches 8272 8271 -1
==========================================
+ Hits 5004 5016 +12
- Misses 7000 7002 +2
+ Partials 5052 5038 -14 see 12 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
@Saviq Seems that it needs also another action:
Can we ignore it? |
@sylvestre I could move the build-snap to Your call! |
base: core22
`base: core22
@sylvestre feel free to push this: diff --git a/.github/workflows/snap.yml b/.github/workflows/snap.yml
index f002d37..84c532c 100644
--- a/.github/workflows/snap.yml
+++ b/.github/workflows/snap.yml
@@ -10,16 +10,6 @@ jobs:
timeout-minutes: 45
- strategy:
- matrix:
- platform:
- - amd64
- - armhf
- - arm64
- # Broken dependencies: - ppc64el
- # https://github.com/mozilla/sccache/issues/1442
- # Broken environment: - s390x
-
steps:
- name: Check out code
uses: actions/checkout@v3
@@ -27,9 +17,8 @@ jobs:
fetch-depth: 0 # needed for version determination
- name: Build and publish the snap
- uses: canonical/actions/build-snap@multiarch
+ uses: canonical/actions/build-snap@release
with:
- architecture: ${{ matrix.platform }}
snapcraft-token: ${{ secrets.SNAPCRAFT_TOKEN }}
publish: ${{ github.event_name == 'pull_request' && github.repository == github.event.pull_request.head.repo.full_name }}
publish-channel: edge/pr${{ github.event.number }} |
Done. |
There's not really a point running a system-wide daemon of sccache. At least not by default. `sccache` forks a local server if one isn't running already, and does it as the current user. The server needs write access to the compilation path, so a central server… doesn't work very well.
Co-authored-by: Sylvestre Ledru <sledru@mozilla.com>
Other arches require untrusted actions.
I think we fixed the server side configuration but we have an error:
|
Fixed, sorry! |
no worries :) |
@Saviq sorry for the dumb question but how do we publish it on snap ? |
Hey, so https://snapcraft.io/docs/releasing-your-app manually, but if you set the |
@sylvestre to get builds from |
This refreshes the snap packaging so that https://snapcraft.io/sccache can be served better.