jenkins-x/jx3-pipeline-catalog

the default tekton catalog for Jenkins X 3.x

Hosted by CD Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

jenkins-x/jx3-pipeline-catalog has 30+ stars and 100+ forks on GitHub, is written in Makefile, and was last pushed on Oct 13, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Type:Curated List / Learning ResourceCategory(s):CI/CD & ReleaseInfrastructure as Code & ConfigDevOps & Observability
Added to GitGenius on October 15th, 2026
Created on September 18th, 2020
Open Issues & Pull Requests: 12 (+0)
GitHub issues: Enabled
Number of forks: 121
Total Stargazers: 30 (+0)
Total Subscribers: 7 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 37.9 days
Mean response time: 37.9 days
90th percentile: 37.9 days
Tracked items: 1

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 703 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-pipeline-catalog is a pipeline catalog that provides reusable Tekton tasks, pipelines, and language-specific packs for Jenkins X 3.x.

The catalog addresses the need for standardized, reusable pipeline components across different programming languages and frameworks. It organizes these components into three main areas: a tasks folder containing reusable steps and triggers, packs that bundle language or framework-specific Tekton pipelines along with supporting files like Dockerfiles and Helm charts, and a helm folder with shared charts imported across the different language packs. This structure allows teams to avoid duplicating pipeline definitions while maintaining consistency across projects.

Teams should adopt this catalog if they run Jenkins X 3.x and want to standardize CI/CD pipelines across multiple projects and languages. The catalog works best for organizations that need language-specific pipeline templates but want to share common patterns. The README emphasizes that teams can fork this catalog to create custom versions tailored to their needs, allowing configuration at global, team, or repository levels. Multiple catalogs can coexist in a single Jenkins X installation, giving developers a choice when creating new projects or importing repositories.

The project maintains active engagement with its community through structured contribution opportunities. Development activity shows consistent updates to the pipeline definitions and packs across different programming languages. The project uses kpt for managing Helm chart upgrades across packs, indicating a deliberate approach to keeping dependencies synchronized. The codebase is primarily organized through Makefiles, suggesting automation-focused development practices for building and maintaining the catalog contents.