From 79dcfd02ddd809d52f336901bc46978388fc89d6 Mon Sep 17 00:00:00 2001 From: Inaki Date: Wed, 8 Jan 2020 18:03:55 +0100 Subject: [PATCH] Update jenkins.md --- docs/jenkins.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/jenkins.md b/docs/jenkins.md index f2821f82..ff3e2ead 100644 --- a/docs/jenkins.md +++ b/docs/jenkins.md @@ -91,8 +91,12 @@ * [youtube - CloudBeesTV: Jenkins Performance: Avoiding Pitfalls, Diagnosing Issues & Scaling for Growth](https://www.youtube.com/watch?v=yTafQ-e84eY) ## Jenkins X +Jenkins X 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. * [itnext.io/tagged/jenkins-x](https://itnext.io/tagged/jenkins-x) * [itnext.io: Jenkins X — Managing Jenkins](https://itnext.io/jenkins-x-managing-jenkins-926f0e0f8bcf) +* Video Tutorials: + * [Youtube: Jenkins X: Continuous Delivery for Kubernetes with James Strachan](https://www.youtube.com/watch?v=BF3MhFjvBTU) + * [Youtube: Kubernetes Package Management with Helm and CI/CD with Jenkins X - Webinar by Neependra Khare](https://www.youtube.com/watch?v=oZOZiL6XIfA&feature=emb_title) ## CI/CD BOTs Use bots to accomplish tasks like merging PR's that have been approved and automatically updating dependencies. Usage of one of these bots might allow us to trigger certain builds based off of specific GitHub tags, it would allow us to only selectively run certain test suites and increase the throughput of the build by only testing changes made in a branch / PR.