From 9ee190b752855e41d4c8d38d1de53271bdce95c1 Mon Sep 17 00:00:00 2001 From: Inaki Date: Thu, 30 Apr 2020 21:18:14 +0200 Subject: [PATCH] Update jenkins.md --- docs/jenkins.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/jenkins.md b/docs/jenkins.md index 3bee8590..6ca4a524 100644 --- a/docs/jenkins.md +++ b/docs/jenkins.md @@ -152,15 +152,15 @@ * [Jenkins BlueOcean 🌟🌟🌟](https://www.jenkins.io/doc/book/blueocean/getting-started/) * [Blue Ocean plugin](https://plugins.jenkins.io/blueocean/) - + - + ## Cloudbees Flow * [**Cloudbees Flow** 🌟🌟🌟](https://www.cloudbees.com/products/flow/overview) * [CloudBees Flow plugin](https://plugins.jenkins.io/electricflow/) - + ## Jenkins X [**Jenkins X**](https://jenkins-x.io) is a specialized Jenkins for Kubernetes: This is how it works from a bird eye the CI/CD: a developer creates a branch, then Jenkins X creates a ephemeral namespace with that branch. The developer tests it and once it is ok, a PR is created, then, the branch is deployed in staging. When I merge it, it goes to QA, and with a manual command "jx promote" it goes to production. Jenkins X deletes automatically after N hours the branch namespace.