feat(ci): Add Fedora RPM package build workflow #961
No reviewers
Labels
No labels
Bug
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/MSC
Matrix/Media
Meta
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
To-Merge
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: continuwuation/continuwuity#961
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "tom/ci-fedora-rpm"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Following PR #950 which introduced the RPM spec and systemd unit files, this adds a comprehensive CI workflow for building, signing, testing, and publishing RPM packages. Includes GPG signing infrastructure with Ed25519 keys and automatic package registry deployment for stable, development, and feature branch builds.
Add documentation for RPM installation methods, repository configuration, and package management. Fix linting issues in spec file for pre-commit compliance.
7406556550
tod38c89f73a
d38c89f73a
to809b6e4f3a
809b6e4f3a
to98775d915c
15662898a0
to5a4627b879
5a4627b879
to4b78ab39e0
4b78ab39e0
toee2557f722
@ -0,0 +81,4 @@
# Aggressive GC since cache restores don't increment counter
echo "CARGO_INCREMENTAL_GC_TRIGGER=5" >> $GITHUB_ENV
- name: Install build dependencies
This step of the workflow should happen after the srpm is generated, and use
dnf builddep <srpm path>
to install the build dependencies listed in the specfile instead of duplicating them here.@ -0,0 +282,4 @@
rpm -qpl "$RPM"
# Actually install it (would need --nodeps if dependencies aren't met)
dnf install -y "$RPM" || rpm -ivh --nodeps "$RPM"
Why does this silently try again with
--nodeps
ifdnf install
fails? The workflow should fail if the dependencies fail to install.ee2557f722
to7be651a307
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.