The Fedora Forge team made progress on Fedora Forge over the past two weeks, including significant infrastructure improvements and new feature development.
Recent Infrastructure Improvements
Over the past two weeks, infrastructure stabilization and user experience improvements progressed significantly, completing most of the planned work.
The Forgejo version detection issue that blocked proper deployment was resolved (#185), making deployments more reliable. A rebase to v13.0/forgejo was completed (#201), staging database pruning was added to control size growth (#174), and a new Konflux pipeline for staging image builds was set up (#198).
FAS integration documentation was expanded, covering team permissions, naming standards, and organization/team mapping (#194, #197, #196). Fedora-focused documentation for issue and pull request templates was created (#199), and workarounds for dependency settings and organization-level project issues were documented (#154, #139).
Repository visibility filtering was configured to hide forks and repos without descriptions from main listings (#172), public user profile visibility was enforced (#166), and personal profile repository creation was disabled (#167). The Pagure migrator UI was enhanced for private ticket mode with clearer instructions (#186).
Most of these changes are now deployed to staging and will be rolled out to production shortly.
The notification system investigation was completed (#193), deciding to pursue native Forgejo email notifications instead of FMN integration. This decision simplifies the notification implementation and reduces long-term maintenance burden.
Current Development Focus
Current work focuses on infrastructure and core features, completing the Forgejo Actions and Runner setup for automated workflows, implementing the native Forgejo email notification system, addressing production issues with the Valkey system, and continuing deployment pipeline improvements.
The CI/Runner infrastructure work is a priority, as it enables automated workflows on Fedora Forge repositories. This work includes VM provisioning, runner environment configuration, webhook integration for Action Run events in Fedora Messaging, and testing frameworks.
Valkey Images Issue
A production issue caused by changes to third-party image availability is being addressed, which resulted in the removal of valkey server images. This has left the system semi-down, with only 2 of 3 instances currently running.
The immediate response is to deploy with in-memory storage as a temporary solution, which will restore full functionality while the team develops a long-term solution.
Email Notifications Implementation
Native Forgejo email notifications are being implemented with a staging-first approach. This includes testing on the staging environment before production rollout, creating a script to update migrated accounts with proper Fedora Accounts email addresses, and developing a custom “forgebot” webhook type for Matrix notifications.
Runner Development Work
The Forgejo Actions/Runner work continues as the team’s focus. This includes setting up dedicated runner infrastructure, configuring runner images and registration, supporting Action Run events in Fedora Messaging, and deploying and testing changes in staging.
Get Involved
Questions or Issues?
- File issues or feature requests: Fedora Forge Issue Tracker
- Chat with the team: Join us in Matrix
- Follow our progress: Current Project Board
Fedora Forge Team