---
title: "#jenkins articles | Hashnode"
description: "Explore 3,555 articles tagged #jenkins on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/jenkins"
---

Tag

# #jenkins

3,555 posts · 1,803 followers

[Randi W](https://hashnode.com/@salesforcegirl) · [2d ago](https://hashnode.com/posts/git-3-0-and-your-salesforce-deployments-what-to-check-now/6afa2abfad2ef7773de87291)

### [Git 3.0 and your Salesforce deployments: what to check now](https://salesforcegirl.hashnode.dev/git-3-0-and-your-salesforce-deployments-what-to-check-now?utm_source=hashnode&utm_medium=feed)

Your metadata won't notice. Your glue might.

5 min read · [salesforcegirl.hashnode.dev](https://salesforcegirl.hashnode.dev/git-3-0-and-your-salesforce-deployments-what-to-check-now?utm_source=hashnode&utm_medium=feed)

[Graphwake](https://hashnode.com/@graphwake) · [3d ago](https://hashnode.com/posts/breaking-change-alerts-from-azure-devops-bitbucket-pipelines-and-jenkins/6af8b0e5a0897f598cfd659c)

### [Breaking change alerts from Azure DevOps, Bitbucket Pipelines and Jenkins](https://graphwake.hashnode.dev/breaking-change-alerts-from-azure-devops-bitbucket-pipelines-and-jenkins?utm_source=hashnode&utm_medium=feed)

Copy-paste setup for Azure DevOps, Bitbucket Pipelines and Jenkins: store the key, add one step, set the live branch, confirm it.

9 min read · [graphwake.hashnode.dev](https://graphwake.hashnode.dev/breaking-change-alerts-from-azure-devops-bitbucket-pipelines-and-jenkins?utm_source=hashnode&utm_medium=feed)

[Adedoyin Ogunsola](https://hashnode.com/@adegram) · [5d ago](https://hashnode.com/posts/built-a-secure-ci-cd-pipeline-with-jenkins-linting-sonarqube-trivy-and-docker-registry-push/6af5c3046772767f01d7815f)

### [Built a Secure CI/CD Pipeline with Jenkins: Linting, SonarQube, Trivy, and Docker Registry Push](https://adehorizon.hashnode.dev/built-a-secure-ci-cd-pipeline-with-jenkins-linting-sonarqube-trivy-and-docker-registry-push?utm_source=hashnode&utm_medium=feed)

The 𝗽𝗶𝗽𝗲𝗹𝗶𝗻𝗲 follows this 𝗼𝗿𝗱𝗲𝗿 Lint (fail fast on cheap issues) Unit tests with coverage SonarQube scan and Quality Gate check Build the image Trivy scan of the image (and IaC config sc

2 min read · [adehorizon.hashnode.dev](https://adehorizon.hashnode.dev/built-a-secure-ci-cd-pipeline-with-jenkins-linting-sonarqube-trivy-and-docker-registry-push?utm_source=hashnode&utm_medium=feed)

[Yuvraj.R](https://hashnode.com/@yuvi21) · [6d ago](https://hashnode.com/posts/understanding-a-real-time-ci-cd-pipeline-with-jenkins-docker-kubernetes-and-argo-cd/6af557d70be5e8491b076096)

### [Understanding a Real-Time CI/CD Pipeline with Jenkins, Docker, Kubernetes and Argo CD](https://build-break-fix-diaries-with-yuvrajj.hashnode.dev/understanding-a-real-time-ci-cd-pipeline-with-jenkins-docker-kubernetes-and-argo-cd?utm_source=hashnode&utm_medium=feed)

A beginner-friendly guide to understanding how Jenkins, Docker, Kubernetes and Argo CD work together to automate application build, testing and deployment.

7 min read · [build-break-fix-diaries-with-yuvrajj.hashnode.dev](https://build-break-fix-diaries-with-yuvrajj.hashnode.dev/understanding-a-real-time-ci-cd-pipeline-with-jenkins-docker-kubernetes-and-argo-cd?utm_source=hashnode&utm_medium=feed)

[Solomon Ndimu](https://hashnode.com/@sololemonsthedev) · [Nov 8](https://hashnode.com/posts/building-an-end-to-end-event-driven-ci-cd-pipeline-with-jenkins-terraform-docker-ansible-minikube-and-floci/6af03249b15941c3419ef031)

### [Building an End-to-End Event- Driven CI/CD Pipeline with Jenkins, Terraform, Docker,Ansible, Minikube and Floci](https://sololemonsthedev.hashnode.dev/building-an-end-to-end-event-driven-ci-cd-pipeline-with-jenkins-terraform-docker-ansible-minikube-and-floci?utm_source=hashnode&utm_medium=feed)

Build a complete event-driven DevOps platform using Jenkins, Terraform, Docker, Kubernetes, Ansible, and Floci.

49 min read · [sololemonsthedev.hashnode.dev](https://sololemonsthedev.hashnode.dev/building-an-end-to-end-event-driven-ci-cd-pipeline-with-jenkins-terraform-docker-ansible-minikube-and-floci?utm_source=hashnode&utm_medium=feed)

[2](https://hashnode.com/posts/building-an-end-to-end-event-driven-ci-cd-pipeline-with-jenkins-terraform-docker-ansible-minikube-and-floci/6af03249b15941c3419ef031)

[Vivian Chiamaka Okose](https://hashnode.com/@vivianokose) · [Nov 7](https://hashnode.com/posts/gitops-argocd-jenkins-real-rollback/6aeed46933856e31f141f6e5)

### [GitOps With ArgoCD and Jenkins: No Cluster Access for CI, and a Real Rollback](https://vivianokose.hashnode.dev/gitops-argocd-jenkins-real-rollback?utm_source=hashnode&utm_medium=feed)

I removed my CI server's access to my cluster. Jenkins now ends at a git commit, ArgoCD deploys, and a real bad release was rolled back with git revert.

10 min read · [vivianokose.hashnode.dev](https://vivianokose.hashnode.dev/gitops-argocd-jenkins-real-rollback?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/gitops-argocd-jenkins-real-rollback/6aeed46933856e31f141f6e5)

[Mahima Singh](https://hashnode.com/@smahima) · [Nov 1](https://hashnode.com/posts/finding-the-real-reasons-jenkins-jobs-fail-elasticsearch-a-hybrid-classifier-and-a-claude-reporting-agent/6ae714b85cd23825aa86fd41)

### [Finding the Real Reasons Jenkins Jobs Fail: Elasticsearch, a Hybrid Classifier and a Claude Reporting Agent](https://smahima.hashnode.dev/finding-the-real-reasons-jenkins-jobs-fail-elasticsearch-a-hybrid-classifier-and-a-claude-reporting-agent?utm_source=hashnode&utm_medium=feed)

Learn how we turned 3000+ chaotic Jenkins jobs into structured, actionable telemetry using Logstash, scikit-learn, and a read-only Grafana MCP server.

10 min read · [smahima.hashnode.dev](https://smahima.hashnode.dev/finding-the-real-reasons-jenkins-jobs-fail-elasticsearch-a-hybrid-classifier-and-a-claude-reporting-agent?utm_source=hashnode&utm_medium=feed)

[Rabin Adhikari](https://hashnode.com/@softverse) · [Oct 30](https://hashnode.com/posts/github-actions-vs-gitlab-ci-vs-jenkins-in-2026-which-ci-cd-tool-fits-your-team/6ae4c1fa5ceaf88286f3a8c1)

### [GitHub Actions vs GitLab CI vs Jenkins in 2026: Which CI/CD Tool Fits Your Team?](https://devopsenginer.hashnode.dev/github-actions-vs-gitlab-ci-vs-jenkins-in-2026-which-ci-cd-tool-fits-your-team?utm_source=hashnode&utm_medium=feed)

By DevOps Enginer – CI/CD Series · Updated for 2026 Quick answer: If your code already lives on GitHub and you want CI/CD with almost no setup or maintenance, GitHub Actions is the default choice in 2

28 min read · [devopsenginer.hashnode.dev](https://devopsenginer.hashnode.dev/github-actions-vs-gitlab-ci-vs-jenkins-in-2026-which-ci-cd-tool-fits-your-team?utm_source=hashnode&utm_medium=feed)

[Karthikeyan Selvaraj](https://hashnode.com/@cloudbites) · [Oct 29](https://hashnode.com/posts/how-to-troubleshoot-jenkins-pipeline-failures-using-rag-and-ai/6ae31a360585efbb2d422f8e)

### [How to Troubleshoot Jenkins Pipeline Failures Using RAG and AI](https://cloudbites.hashnode.dev/how-to-troubleshoot-jenkins-pipeline-failures-using-rag-and-ai?utm_source=hashnode&utm_medium=feed)

For DevOps engineers, CI/CD specialists, SREs, and learners exploring RAG and AI-powered Jenkins troubleshooting and root cause analysis.

8 min read · [cloudbites.hashnode.dev](https://cloudbites.hashnode.dev/how-to-troubleshoot-jenkins-pipeline-failures-using-rag-and-ai?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/how-to-troubleshoot-jenkins-pipeline-failures-using-rag-and-ai/6ae31a360585efbb2d422f8e)

[Waqas Shahid](https://hashnode.com/@practicaldevblog) · [Oct 27](https://hashnode.com/posts/jenkins-explained-the-original-ci-cd-workhorse/6ae0c42d102666f423b4578d)

### [Jenkins Explained: The Original CI/CD Workhorse](https://practicaldevblog.hashnode.dev/jenkins-explained-the-original-ci-cd-workhorse?utm_source=hashnode&utm_medium=feed)

Introduction Before GitHub Actions and GitLab CI made pipelines a checkbox, there was Jenkins: an open-source automation server, released in 2011, that has run builds, tests, and deployments for a gen

2 min read · [practicaldevblog.hashnode.dev](https://practicaldevblog.hashnode.dev/jenkins-explained-the-original-ci-cd-workhorse?utm_source=hashnode&utm_medium=feed)
