Sharda Edke’s Post

💡 Day 17 – How Jenkins Works (Simple Explanation) Yesterday, we learned that Jenkins is a tool used for automating build, test, and deployment — but how does it actually work? 🤔 Let’s understand step by step 👇 1️⃣ Developer pushes code to GitHub or GitLab. 2️⃣ Jenkins detects the new code (using a webhook or schedule). 3️⃣ Jenkins Pipeline starts — a series of automated steps written in a file called Jenkinsfile. 4️⃣ It can: 🔹 Build the code 🔹 Run tests 🔹 Create Docker images 🔹 Deploy to servers or cloud Every step is fully automated — no manual clicks needed! 💪 Jenkins uses plugins to connect with almost any tool — like Git, Docker, Kubernetes, AWS, etc. This makes it super flexible for all kinds of projects. In simple words: 👉 Jenkins is like your project’s robot assistant — it builds, tests, and deploys while you focus on coding. 🤖

Before submitting your code for review on Github, execute this critical command git rebase -i This will give you an opportunity to take all of the commits you've made in your branch so far and smash them into a single commit. This cleans up your history in the event that the maintainer forgets to squash on merge. You'll be presented with an interactive prompt that allows you to choose which commits you want squashed. Simply replace the first word before each commit with an s or squash to squash that commit. After saving, you'll have an opportunity to write the commit message representing all of the changes. This is a good opportunity to summarize the work completed. I believe most of my followers should know about this but everyone starts somewhere and I am sure some beginners could benefit. _________________________________________ I’ve bundled 𝟱 𝗿𝗲𝗮𝗹-𝘄𝗼𝗿𝗹𝗱 𝗗𝗲𝘃𝗢𝗽𝘀 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀 you can do with just your laptop, some curiosity, and a free #𝗔𝘇𝘂𝗿𝗲 or #𝗔𝗪𝗦 account. These aren’t hello-world tutorials, they mirror what DevOps engineers actually do at work: • Provision infrastructure with 𝗧𝗲𝗿𝗿𝗮𝗳𝗼𝗿𝗺 • Automate deployments using 𝗚𝗶𝘁𝗛𝘂𝗯 𝗔𝗰𝘁𝗶𝗼𝗻𝘀 • Run and scale apps with 𝗞𝘂𝗯𝗲𝗿𝗻𝗲𝘁𝗲𝘀 • Monitor everything using 𝗣𝗿𝗼𝗺𝗲𝘁𝗵𝗲𝘂𝘀 & 𝗚𝗿𝗮𝗳𝗮𝗻𝗮 • Manage 𝗺𝘂𝗹𝘁𝗶𝗽𝗹𝗲 𝗲𝗻𝘃𝗶𝗿𝗼𝗻𝗺𝗲𝗻𝘁𝘀 like dev & prod • 𝗦𝘁𝗮𝗿𝘁 𝗵𝗲𝗿𝗲:https://lnkd.in/eS3t5NwE

🤖 Introducing the GitLab → Jira Webhook Bot: Automated Failure Tracking I’ve built a webhook service that automatically creates and manages Jira tickets based on GitLab pipeline events.. Here's how it works: - Upon a pipeline failure, the bot utilizes JQL to check for existing failure tickets related to the same branch or repository. If none is found, it automatically generates a new Jira issue. This issue includes an ADF-formatted description, essential pipeline and commit details, as well as the last 20 log lines for comprehensive context. - The bot also ensures seamless collaboration by adding the commit author as a watcher, leveraging the Jira Cloud user search API. - Subsequently, when the pipeline successfully completes, the bot adds a status comment and transitions the issue to "Done" using a configurable transition ID. 🔒 Security Measures: - Implementation of HMAC-SHA256 signature verification for GitLab webhooks. - Utilization of async locking to prevent duplicate ticket creation during parallel webhook triggers (I faced this issue with nested pipelines). - Log sanitation process to remove ANSI escape sequences and section markers from GitLab traces. - Configuration exclusively through environment variables to enhance security (no hardcoded secrets). Built with FastAPI, Requests, and asyncio, running behind Uvicorn. 📂 For those interested in exploring the full source code and setting up the system, detailed instructions can be found on GitHub: https://lnkd.in/eN2_-jwT #Automation #Webhooks #DevOps #Python #FastAPI #GitLab #Jira #CICD #SRE

🚀 Why I Choose Jenkins Over GitHub Actions for CI/CD When setting up a CI/CD pipeline, the first question that usually comes up is: 👉 “Why not just use GitHub Actions? It’s built in and so convenient!” True — GitHub Actions is an amazing tool for automation and integration within the GitHub ecosystem. But after comparing both for a real-world project, I decided to go with Jenkins, and here’s why: 1️⃣ Full Control and Flexibility Jenkins gives me complete control over the build environment, pipelines, and plugins. I can customize everything — from node configurations to secret management — without worrying about external restrictions or billing tiers. 2️⃣ Vendor Independence GitHub Actions works great inside GitHub, but it ties your CI/CD tightly to a single platform. Jenkins, being open-source and self-hosted, keeps the setup portable and cloud-agnostic — I can move my infrastructure between providers like Hetzner, AWS, or GCP without changing workflows. 3️⃣ Scalability and Extensibility With Jenkins, scaling build agents across nodes or integrating custom tools (Vault, ArgoCD, SonarQube, etc.) is straightforward. Its plugin ecosystem remains one of the most extensive in CI/CD. 4️⃣ Cost and Control Over Compute Running Jenkins on my own infrastructure (e.g., Kubernetes or Docker) means I control the compute cost and performance. No hidden runner limitations or minute-based billing. 5️⃣ Security and Secrets Management Integrating Jenkins with Vault gives me a centralized, auditable way to manage secrets — a level of security control that’s harder to achieve with GitHub-hosted runners. 💡 In short: GitHub Actions is great for simplicity and small-to-medium workflows. Jenkins shines when you need deep customization, infrastructure control, and scalability — especially in multi-environment or self-hosted setups. Both tools are powerful — the choice depends on your project’s long-term vision. For mine, Jenkins fit the DevOps architecture I’m building perfectly. Tell me in the comments which tool are you currently using (actions, gitlab ci, jenkins...) #DevOps #CICD #TradeOff #Dev

Excited to share a quick guide on setting up GitHub Webhooks with Jenkins for automated CI/CD pipelines! This automates builds on code changes, saving time and ensuring 24/7 triggering. Here's a step-by-step walkthrough based on my recent practice: Connect to AWS Instance: SSH into your AWS EC2 instance and verify Jenkins is installed and running (e.g., via jenkins --version and systemctl status jenkins). Access Jenkins: Open your browser and connect to Jenkins at http://<instance-ip>:8080. Log in and set up if needed. Set Up Webhook in GitHub: Go to your repository settings > Webhooks > Add webhook. Configure Webhook Details: Enter the Payload URL (e.g., http://<jenkins-url>/github-webhook/), set Content Type to application/json, and select events like "Just the push event." Test Delivery: Refresh the page and check the "Recent Deliveries" section to ensure the last delivery was successful (green checkmark). Prepare for Code Changes: In Jenkins, ensure the GitHub webhook trigger is enabled in your job/pipeline configuration. If not, toggle it on. Make Code Changes: Edit your code (e.g., in a Maven project), commit, and push to the main branch. Create Jenkins Pipeline: Use this sample script in your Jenkinsfile or pipeline job: text pipeline { agent any triggers { githubPush() } tools { maven 'maven' } stages { stage('Checkout') { steps { git branch: 'main', url: 'https://lnkd.in/gXPh6NXc' } } stage('Build') { steps { sh "mvn clean package" } } } } Verify Auto-Trigger: After pushing changes, head back to Jenkins—watch the pipeline trigger automatically (e.g., build #5 kicks off without manual intervention). This setup streamlines devops workflows! If you're into CI/CD, try it out and let me know your tips. #DevOps #Jenkins #GitHub #CICD #Automation

🚀 Automating Deployment with Jenkins & GitHub Actions! In my latest project, I implemented a CI/CD pipeline using both Jenkins and GitHub Actions — combining the best of both worlds to achieve seamless automation from code commit to deployment. 🔧 Here’s what I did: Used GitHub Actions for continuous integration — automatically building, testing, and validating every pull request. Integrated Jenkins for continuous deployment — managing the delivery pipeline, containerizing the application using Docker, and deploying to AWS with zero downtime. Configured webhooks between GitHub and Jenkins to trigger builds on every new commit. Ensured security and scalability by managing credentials with AWS Secrets Manager and using Nginx caching for optimized frontend performance. 💡 Key takeaway: CI/CD isn’t just about automation — it’s about speed, reliability, and developer confidence. With this setup, every code change now flows smoothly from development to production with minimal manual intervention. 🌐 Tech stack: React + Vite + Tailwind CSS | Firebase | Docker | Jenkins | GitHub Actions | AWS (S3 & EC2) #DevOps #CICD #Jenkins #GitHubActions #Automation #Docker #AWS #SoftwareEngineering #WebDevelopment #CloudComputing

💻 - Git Week 2 Day 3 – Ignoring, Viewing & Reverting Changes Today I learned how to manage what Git tracks, view what’s changed, and fix mistakes if something goes wrong. These commands are essential for keeping repositories clean and organised — especially when working in teams or deploying to production. ⸻ 🚫 Ignoring Files with .gitignore Not every file in a project needs to be tracked — things like logs, temporary files, and environment variables should be ignored. You can create a .gitignore file to tell Git which files to skip: Example: echo "*.log" > .gitignore This command creates a .gitignore file and ignores all files ending with .log. You can edit this file manually or create it directly on GitHub before pushing your repository. 🔍 Viewing Changes with git diff Before committing, you can see exactly what’s changed since your last save point: git diff This shows all modified lines that haven’t been staged yet — helpful for reviewing before committing. You can also compare two commits or branches, for example: git diff master This compares your current branch against the master branch. 🧹 Unstaging Files with git restore If you’ve added something by mistake with git add, you can unstage it before committing: git restore --staged file This removes the file from the staging area but keeps your changes safe in the working directory. ⸻ Learning how to ignore, review, and revert changes gave me a much clearer understanding of how Git tracks progress — and how to stay in control of my repository history. ⸻ Next Up: I’ll be diving into remote repositories — learning how to connect local work to GitHub using commands like git remote add, git push, and git pull. If you’re following my DevOps journey, stay tuned for how I connect my local projects to the cloud 🌐 #Git #DevOpsJourney #VersionControl #GitHub #CloudComputing #LearningInPublic

🚀 Your Ultimate DevOps Command Cheat Sheet is Here! Ever found yourself searching for that exact Docker command or Kubernetes syntax in the middle of a deployment? We've all been there. That's why I've compiled a comprehensive DevOps cheat sheet covering the essential commands you need daily. Here are the key areas covered: 🐧 Linux Fundamentals – From basic file ops to advanced text processing with awk/sed 🐳 Docker & Containerization – Build, run, and manage containers and images ☸ Kubernetes Orchestration – Deploy, scale, debug, and manage clusters 🛠 Terraform & Infrastructure as Code – Plan, apply, and manage cloud resources 📦 Helm Charts – Simplify K8s app deployment and management 🔗 Git & GitHub – Version control and collaboration commands Whether you're a beginner or a seasoned engineer, this cheat sheet is your quick-reference guide to streamline workflows and boost productivity. 👉 Want the full PDF cheat sheet? DM me with "DevOps Cheat Sheet" and I’ll send it your way! #DevOps #CloudComputing #Kubernetes #Docker #Terraform #DeveloperTools