openSUSE/open-build-service

Build and distribute Linux packages from sources in an automatic, consistent and reproducible way #obs

Owned by SUSE

View on GitHub ↗Jump to charts ↓Open shareable report →

openSUSE/open-build-service has 1k+ stars and 450+ forks on GitHub, is written in Ruby, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 16 minutes ago
Added to GitGenius on October 12th, 2026
Created on July 14th, 2011
Open Issues & Pull Requests: 1,232 (+0)
GitHub issues: Enabled
Number of forks: 498
Total Stargazers: 1,084 (+0)
Total Subscribers: 54 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 23.5 hours
Mean response time: 153.7 days
90th percentile: 217.2 days
Tracked items: 538

Maintainer activity

12 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 8% of issues opened in the past year have never received a reply. 66% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "P2" is answered fastest, typically in under an hour, while "scmsync" waits about 7 days. 26% of tracked open issues have had no activity in three months. 77% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 166
New in 7 days: 9
Closed in 7 days: 11
Avg open age: 927 days
Stale 30+ days: 147
Stale 90+ days: 95

Recent activity

Opened in 7 days: 9
Closed in 7 days: 11
Comments in 7 days: 1
Events in 7 days: 15

Top labels

  • Bug (381)
  • Frontend (379)
  • Feature (77)
  • request-redesign (60)
  • Backend (54)
  • scmsync (44)
  • scm-ci (38)
  • P2 (31)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Open Build Service is a system for building and distributing binary packages from sources in an automatic, consistent, and reproducible way across multiple operating systems and hardware architectures.

The tool addresses the challenge of maintaining package builds across diverse Linux distributions and platforms. It automates the process of compiling source code and generating binary packages for different targets, eliminating manual build processes and ensuring consistency. The system consists of a backend that handles core build functionality, a web-based frontend with an XML API for interaction, and a separate command-line client for programmatic access.

Organizations should adopt this tool if they need to maintain packages across multiple distributions such as Debian, Ubuntu, Fedora, CentOS, and Arch Linux, or if they require reproducible builds across different architectures. It suits projects ranging from individual package maintenance to full distribution releases. The tool supports various package formats including RPM, DEB, and AppImage, making it valuable for teams managing complex multi-platform packaging workflows. For simpler single-distribution packaging needs, lighter-weight solutions may suffice, but OBS excels when consistency and automation across many targets become critical.

Development activity shows sustained engagement through community channels including IRC and mailing lists where contributors can discuss ongoing work. The project maintains organized source code structure with clear separation between the Rails-based frontend API layer and the Perl backend implementation. Installation is supported through multiple pathways including a pre-configured appliance for production deployments, package-based installation with setup wizards, and Docker Compose for development environments, indicating attention to different user needs. The project provides comprehensive documentation including an administrator guide for complex distributed setups, suggesting maturity in supporting varied deployment scenarios.