jenkins-x/jx3-versions

jx3-versions is a version stream repository that maintains pinned versions and configurations for Helm charts, container images, Git repositories,...

Hosted by CD Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

jenkins-x/jx3-versions has 10+ stars and 40+ forks on GitHub, is written in Go Template, and was last pushed on Oct 14, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 46 minutes ago
Added to GitGenius on October 15th, 2026
Created on April 14th, 2020
Open Issues & Pull Requests: 14 (+0)
GitHub issues: Enabled
Number of forks: 48
Total Stargazers: 13 (+0)
Total Subscribers: 8 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.8 hours
Mean response time: 3.8 hours
90th percentile: 3.8 hours
Tracked items: 1

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

jx3-versions is a version stream repository that maintains pinned versions and configurations for Helm charts, container images, Git repositories, command-line tools, and other resources used by Jenkins X 3.x clusters.

The repository solves the problem of coordinating compatible versions across the many components that make up a Jenkins X installation. Rather than allowing each component to float to its latest version independently, the version stream approach pins specific versions and configurations in a centralized location. This ensures that all components work together reliably and that cluster boots are reproducible. The repository organizes these pinned versions into logical directories: charts for Helm chart versions and their configurations, images for container images, packages for command-line tools, git for Git repository references, and additional directories for cluster boot jobs, scheduler configurations, and secret mappings.

Teams should adopt this repository if they are running Jenkins X 3.x and need a stable, tested set of component versions for their clusters. It is essential for anyone bootstrapping a new Jenkins X cluster or maintaining an existing one, as it provides the authoritative version stream that the boot process consults. The repository is not a tool to be adopted in isolation but rather a reference that Jenkins X itself depends on; it is most relevant to operators managing Jenkins X infrastructure rather than end users of Jenkins X.

The project receives contributions across its version definitions and configuration files, with activity distributed among updates to multiple component directories rather than concentrated in a single area. Changes span the charts, images, packages, and configuration sections, indicating ongoing maintenance of the various resource types the version stream tracks. The project maintains documentation references pointing to the Jenkins X concepts around version streams, suggesting that updates are accompanied by awareness of the broader system design.