Skip to content

Ravi Sir's Cards › DevOps

Chapter 23: Jenkins Fundamentals, Install and Architecture: Cards

मराठी cards · Open the chapter

Revision cards

What Jenkins is. Manual builds and tests are slow and people forget steps. — Revision card 1 of 8: What Jenkins is · Download PNG · Open card page

Lesson: 23.1 What Jenkins is

Integration, delivery, deployment. These three words sound the same but mean different stops in the pipeline. — Revision card 2 of 8: Integration, delivery, deployment · Download PNG · Open card page

Lesson: 23.2 Integration, delivery, deployment

Controller and agents. Running every build on one machine is slow and unsafe. — Revision card 3 of 8: Controller and agents · Download PNG · Open card page

Lesson: 23.3 Controller and agents

JENKINS_HOME: where Jenkins keeps everything. If this folder is lost, all jobs, history and settings are lost. — Revision card 4 of 8: JENKINS_HOME: where Jenkins keeps everything · Download PNG · Open card page

Lesson: 23.4 JENKINS_HOME

Environment variables and artifacts. Builds need to know their number, commit and folder, to name and track outputs. — Revision card 5 of 8: Environment variables and artifacts · Download PNG · Open card page

Lesson: 23.5 Environment variables and artifacts

Linux package install: follow today's docs. Old blog commands often fail because keys and Java versions change. — Revision card 6 of 8: Linux package install: follow today's docs · Download PNG · Open card page

Lesson: 23.6 Linux package install — follow today's docs

Other ways to run Jenkins. Teams run Jenkins in different places. Each needs data kept safe and a secure way in. — Revision card 7 of 8: Other ways to run Jenkins · Download PNG · Open card page

Lesson: 23.7 WAR, Docker, Kubernetes, Nginx, firewall

Jenkins CLI from your own controller. Clicking is slow for repeated admin work. — Revision card 8 of 8: Jenkins CLI from your own controller · Download PNG · Open card page

Lesson: 23.8 CLI, from your own controller

Interview cards

What is Jenkins? An open-source automation server that runs build, test and deploy jobs when code changes, on a timer, or by hand. — Interview card 1 of 8: What is Jenkins? · Download PNG · Open card page

Lesson: 23.1 What Jenkins is

Continuous Delivery vs Continuous Deployment? Delivery: every good build is ready to release; a human clicks deploy. Deployment: it goes to production automatically. — Interview card 2 of 8: Continuous Delivery vs Continuous Deployment? · Download PNG · Open card page

Lesson: 23.2 Integration, delivery, deployment

Explain Jenkins controller and agent. The controller stores jobs, schedules builds and shows results. Agents run the build steps. — Interview card 3 of 8: Explain Jenkins controller and agent. · Download PNG · Open card page

Lesson: 23.3 Controller and agents

What is in JENKINS_HOME, and why back it up? Jobs, build history, plugins, config and secrets. It is all of Jenkins; no other database. — Interview card 4 of 8: What is in JENKINS_HOME, and why back it up? · Download PNG · Open card page

Lesson: 23.4 JENKINS_HOME

Name some Jenkins build environment variables. BUILD_NUMBER, JOB_NAME, WORKSPACE, GIT_COMMIT, BRANCH_NAME (multibranch). — Interview card 5 of 8: Name some Jenkins build environment variables. · Download PNG · Open card page

Lesson: 23.5 Environment variables and artifacts

How do you install Jenkins on Linux? Install a supported Java, add the Jenkins repo and key, install the package, enable the service. — Interview card 6 of 8: How do you install Jenkins on Linux? · Download PNG · Open card page

Lesson: 23.6 Linux package install — follow today's docs

How do you run Jenkins in Docker safely? Use jenkins/jenkins:lts, keep JENKINS_HOME on a volume, and put HTTPS in front. — Interview card 7 of 8: How do you run Jenkins in Docker safely? · Download PNG · Open card page

Lesson: 23.7 WAR, Docker, Kubernetes, Nginx, firewall

How do you start a Jenkins job from a terminal? Use jenkins-cli.jar or the REST API with your user and API token. — Interview card 8 of 8: How do you start a Jenkins job from a terminal? · Download PNG · Open card page

Lesson: 23.8 CLI, from your own controller

Comparison cards

CI vs CD (Continuous Integration vs Continuous Delivery). CI (Continuous Integration): every code push is built and tested automatically, many times a day.CD (Continuous Delivery): every change that passes CI is packed and made ready to release to users. — Comparison card 1 of 3: CI vs CD (Continuous Integration vs Continuous Delivery) · Download PNG · Open card page

Lesson: 23.2 Integration, delivery, deployment

Controller vs Agent. Controller: the main Jenkins server with UI, jobs and schedule.Agent: a machine that runs build steps. — Comparison card 2 of 3: Controller vs Agent · Download PNG · Open card page

Lesson: 23.3 Controller and agents

Jenkins as Linux package vs Docker container. Package: installed on the server as a service.Docker: runs from the jenkins/jenkins image. — Comparison card 3 of 3: Jenkins as Linux package vs Docker container · Download PNG · Open card page

Lesson: 23.7 WAR, Docker, Kubernetes, Nginx, firewall