Repository navigation
feat(ci): publish armv7 release binaries for Raspberry Pi - #73
Merged
Merged
Conversation
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.
Avant
Le workflow Release ne publie qu'un tarball
fleet-linux-x86_64.tar.gz. Un Raspberry Pi (armv7) ne peut pas l'utiliser.Après
release.yml: jobbuilden matrix →x86_64-unknown-linux-gnu(natif) +armv7-unknown-linux-gnueabihf(viacross, version épinglée 0.2.5), puis un jobpublishconsolide les artefacts (upload-artifact/download-artifactmerge-multiple) et crée la release GitHub avec les deux tarballs :fleet-linux-x86_64.tar.gzetfleet-linux-armv7.tar.gz.permissions: contents: writeexplicite surpublish(robustesse).Objectif : sur le Pi 2, la pipeline
fleettéléchargefleet-linux-armv7.tar.gz, la décompresse et remplace les binaires~/.cargo/bin/fleet/fleetd, puis redémarre le service.Vérification