# Jenkins X — Cloud Native CI/CD for Kubernetes

> Jenkins X provides automated CI/CD pipelines with GitOps promotion, preview environments on pull requests, and Tekton-based builds natively on Kubernetes.

## Install

Save as a script file and run:

# Jenkins X — Cloud Native CI/CD for Kubernetes

## Quick Use
```bash
# Install the jx CLI
curl -L https://github.com/jenkins-x/jx/releases/latest/download/jx-linux-amd64.tar.gz | tar xzv
sudo mv jx /usr/local/bin/
# Create a cluster with Jenkins X
jx create cluster gke --skip-login
# Import an existing project
jx project import
```

## Introduction
Jenkins X reimagines CI/CD for the Kubernetes era. Unlike traditional Jenkins, it is built from the ground up around GitOps principles, using Tekton Pipelines for build execution and Lighthouse for webhook handling. It automates the entire path from code commit to production deployment with environment promotion via pull requests.

## What Jenkins X Does
- Creates Tekton-based CI/CD pipelines automatically from detected project types
- Generates preview environments for every pull request for stakeholder review
- Manages environment promotion (staging, production) through GitOps pull requests
- Provides ChatOps commands via Lighthouse for approving and merging changes
- Scaffolds new projects with build packs that include Dockerfiles, Helm charts, and pipelines

## Architecture Overview
Jenkins X v3 uses a GitOps-driven architecture. The cluster state is stored in a Git repository and reconciled by a Kubernetes operator. Lighthouse handles incoming webhooks from GitHub, GitLab, or Bitbucket and triggers Tekton PipelineRuns. The jx CLI and a web-based dashboard provide user interfaces. Vault or external secret managers handle credentials.

## Self-Hosting & Configuration
- Install on GKE, EKS, AKS, or any conformant Kubernetes cluster using the `jx` CLI or Terraform modules
- Define pipelines in `.lighthouse/` directory using Tekton YAML or simplified pipeline catalog references
- Configure environment repositories for staging and production GitOps promotion
- Use Vault, Google Secret Manager, or AWS Secrets Manager for credential storage
- Customize build packs to match organizational standards for Docker builds and Helm charts

## Key Features
- Automatic semantic versioning of releases based on conventional commit messages
- Preview environments with unique URLs for every pull request
- Pipeline catalog system for reusable, parameterized build steps
- Multi-cluster support for separating build infrastructure from deployment targets
- Built-in Helm chart management for application packaging and deployment

## Comparison with Similar Tools
- **Traditional Jenkins** — plugin-based CI server; Jenkins X is Kubernetes-native with GitOps, no shared Jenkins server
- **Argo CD** — focuses on GitOps deployment; Jenkins X includes CI pipelines and preview environments
- **Tekton** — raw pipeline engine; Jenkins X adds opinionated workflows on top of Tekton
- **GitLab CI/CD** — integrated with GitLab; Jenkins X is platform-agnostic
- **Flux** — GitOps controller for Kubernetes; Jenkins X adds CI, preview envs, and ChatOps

## FAQ
**Q: Is Jenkins X related to Jenkins?**
A: Jenkins X originated from the Jenkins community but is a separate project with different architecture. It does not run a Jenkins server.

**Q: Which Git providers are supported?**
A: GitHub, GitLab, and Bitbucket are supported through the Lighthouse webhook handler.

**Q: Can I use Jenkins X without a cloud provider?**
A: Yes. It runs on any Kubernetes cluster, including on-premises or local clusters like kind or minikube.

**Q: What happened to Jenkins X v2?**
A: v2 used a Jenkins server and custom CRDs. v3 replaced it with a simpler GitOps model using Tekton and Lighthouse, and is the actively maintained version.

## Sources
- https://github.com/jenkins-x/jx
- https://jenkins-x.io/v3/

---
Source: https://tokrepo.com/en/workflows/asset-7cd2d3a5
Author: Script Depot