SUSE/BCI-dockerfile-generator

Generator for the SUSE Linux BCI Build recipes

Owned by SUSE

View on GitHub ↗Jump to charts ↓

SUSE/BCI-dockerfile-generator has 10+ stars and 30+ forks on GitHub, is written in Python, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 52 minutes ago
Added to GitGenius on October 12th, 2026
Created on June 9th, 2022
Open Issues & Pull Requests: 41 (+0)
GitHub issues: Enabled
Number of forks: 37
Total Stargazers: 17 (+0)
Total Subscribers: 8 (+0)

Repository Insights (GitGenius)

Median issue/PR response: N/A
Mean response time: 17.8 hours
90th percentile: 0.0 hours
Tracked items: 141

How this project is maintained

Practically every issue opened in the past year has drawn a reply. 95% of issues opened in the past year have since been closed. Three people close 99% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 6
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 328 days
Stale 30+ days: 5
Stale 90+ days: 4

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 2

Top labels

  • enhancement (3)
  • documentation (1)
  • good first issue (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

BCI Dockerfile Generator is a Python-based automation tool that generates build recipes for SUSE Linux container images.

The tool solves the problem of maintaining consistent, reproducible build definitions across multiple container images by using templating logic to autogenerate Dockerfiles and kiwi build descriptions. It works by defining container specifications in Python code, then rendering those specifications into build recipes that can be deployed to the Open Build Service. The project includes two major components: templating logic within the bci_build module that handles recipe generation, and GitHub automation within the staging module that renders templates into separate branches and synchronizes them to OBS.

Teams maintaining multiple container images should consider this tool if they need to keep build definitions in sync across different formats and deployment targets. It suits projects where container specifications need to be version-controlled and automatically synchronized to a build service. The tool is specifically designed for the SUSE BCI project and its integration with the Open Build Service, making it most relevant for organizations using that infrastructure.

The project maintains active development with regular contributions to both the core templating system and documentation. Contributors are expected to format code using ruff and run the full test suite before submitting changes. The project includes comprehensive documentation built with Sphinx and uses Jinja2 templating for generating container-specific README files, with helper templates provided for standardized sections like licensing information and access controls. Unit tests are run as part of the contribution workflow, and documentation building is validated during the review process.