Repository navigation
CI: build, verify and negative-test the sargo image - #1
Merged
Merged
Conversation
…ore privileged steps
…when another package fails
…e on cancel, blank PKGBUILD_ONLY
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Builds the sargo image on every push and pull request to main, then runs
verify.shand the negative test on it, on a nativeubuntu-24.04-armrunner.Change
.github/workflows/image.yml: unit tests (style check,test-android-image.py,test-backends.sh), then the in-repo packages, the image, verify and the negative test. The image and build log are uploaded for 7 days.contents: readonly, no secrets, every action pinned by SHA, and checkout does not persist credentials. The image carries no SSH key or Wi-Fi credentials. Only the kernel is cached, keyed on its own directory; every other in-repo package is rebuilt each run.PKGBUILD_ONLYindocker/build-packages.sh(passed through byprovision.sh) builds only the named in-repo recipes and skips the manifest components and AUR rebuilds. Unset, the build is unchanged. It also serves single-package iteration:PKGBUILD_ONLY=moarchy.docker/Dockerfile.builderinstalls megapixels' build dependencies, which a full build only had because a manifest component'smakepkg -spulled them in; its PKGBUILD now declares gperf and libpulse (pkgrel 2).scripts/fetch-published.sh <dir>fills in everything else from the signed[moarchy]repo the manifest names. It verifies the database and every package againstpkgbuilds/moarchy-keyring(the primary key fingerprint fromVALIDSIG), records each hash in.build-manifestsopkgset_vouchedaccepts them, and removes anything the manifest does not vouch for. The published repo can trail the manifest pins, so a CI image tests this tree, not a release.image/verify.sh: three stale checks fixed. The device tile isorg.moarchy.Device.plugin.desktop. The shell must have noQuickshell.I3imports and at least oneQuickshell.Hyprlandimport, matching omarchy-config's inverted A2.Not covered
Testing
Locally,
fetch-published.shagainst the real repo, with a manifest vouching for all but three packages: it fetched and vouched the three, removed an unvouched file, and refused a package whose signature had been swapped. It also refused a tree package missing from the manifest and a validly signed package served under another package's filename.CI on this branch: verify reports all checks passed (including the online resize2fs growth), and the negative test catches all 11 planted defects. About 11 minutes with the kernel cached.