GitHub Actions Runners: Hosted vs Self-Hosted Explained

#100DaysOfDevOps - Day Forty - Four After completing a full Jenkins-based CI pipeline over the last few days, I wanted to take time to talk about GitHub Actions properly before jumping into writing workflows. Today was more about concepts and structure than hands-on work. What I covered: ✅ what GitHub Actions is ✅ why it is one of the most popular CI tools today ✅ how it compares to Jenkins ✅ why GitHub Actions feels simpler when your code already lives in GitHub ✅ why Jenkins is still valuable because it can work across multiple platforms ✅ the role of: GitHub Actions documentation GitHub Marketplace ✅ GitHub Actions concepts like: workflow job runner secrets triggers One thing that really stood out to me today is that the core ideas behind CI tools are usually not different. A lot of the time, what changes is the naming, the interface, the level of setup required, etc. So in many ways, learning Jenkins first made GitHub Actions easier to understand, because I could already recognize the same ideas under different names. When you understand the concept deeply, moving between tools becomes much easier. YouTube Video Link: https://lnkd.in/eBpD3YHN #DevOps #100DaysOfDevOps #GitHubActions #Jenkins #CICD #ContinuousIntegration #Automation #GitHub #PlatformEngineering #CloudEngineering #LearningInPublic #TechdotSam

🚀 Day 26 of #90DaysOfDevOps |: Mastering the GitHub CLI (gh) Efficiency is the name of the game in DevOps. Today, I stepped away from the web UI and moved my workflow entirely into the terminal using the GitHub CLI. While many of us are used to standard git commands, gh takes it a step further by allowing us to manage the entire GitHub ecosystem (Issues, PRs, Actions) without leaving the command line. 🔑 Key Takeaways from Day 26: ♦️ Seamless Authentication: Explored how gh auth handles everything from Web-based logins to Personal Access Tokens (PATs) for automated environments. ♦️ PR Management: Learned to checkout, diff, and merge Pull Requests directly from the terminal. My favorite? gh pr checkout <number>—it saves so much time when reviewing a teammate's code. ♦️Automation Power: Realized the potential of gh issue for CI/CD. Imagine a Jenkins build failing and automatically triggering a GitHub Issue with the error logs attached. That's true "Ops" in DevOps. 🛠️ Why use CLI over GUI? Speed: No more hunting through menus. Scriptability: You can bake GitHub actions into your local bash scripts. Focus: Stay in your IDE/Terminal flow. GitHub : https://lnkd.in/g44eYvdQ #90DaysOfDevOps #DevOpsKaJosh #TrainWithShubham

🔥 Git & GitHub — Every DevOps Engineer's Best Friend! Today I learned Git from scratch and pushed my FIRST code to GitHub! 🎊 Here's what I learned: Git = Version control tool GitHub = Cloud for your code Like Microsoft Word's "Track Changes" but 1000x more powerful! 💪 CORE WORKFLOW: git init → Start tracking a project! git status → Most used command! → See what changed! git add . → Stage all changes! git commit -m "message" → Save a snapshot! 📸 → Like a checkpoint in a video game! 🎮 git push → Upload to GitHub! ☁️ BRANCHES — Mind blowing! 🤯 git branch feature-login → Create parallel universe! git checkout feature-login → Switch to it! Work safely without breaking main code! git merge feature-login → Combine when done! ✅ 🌟 Most amazing part: Same folder! Different files! Based on which branch you are on! 🌌 Master branch = no login page Feature branch = has login page Switch branch = files appear/disappear! 🔥 Just pushed my first repo to GitHub! 🎊 Check it out: https://lnkd.in/gf8UKsHP #Git #GitHub #DevOps #AWS #LearningInPublic #CloudComputing #Fresher #TechJourney #DevOpsEngineer #VersionControl #Coding

Cloud Tech Tip #19 — Git & GitHub: The Foundation of Every Modern Engineering Team If you're not using Git properly, you're making your job harder than it needs to be. Git and GitHub are the tools I use every single day — more than any AWS service. Here's why they matter and what every engineer should know: What is Git? Git is a distributed version control system. Every change you make to code is tracked, reversible, and auditable. What is GitHub? GitHub is where your Git repositories live remotely. It's your code's home base — and with GitHub Actions, it's also your CI/CD pipeline. The core benefits: → 📜 Full audit trail — every change is logged with who made it and why → 🔀 Branching — work on features in isolation without breaking production → 🤝 Collaboration — multiple engineers on the same codebase without stepping on each other → ♻️ Rollbacks — something broke? Revert to a previous state in seconds → 🚀 GitHub Actions — automate deployments, tests, and infrastructure changes directly from your repo Branching strategy that works: → main — production ready code only → dev — integration branch for active development → feature/your-feature — isolated work per feature or fix Never commit directly to main. Always open a Pull Request. Always get a review. Git isn't just a tool. It's how engineering teams stay organized, move fast, and ship confidently. #Git #GitHub #DevOps #CloudEngineering #VersionControl #CICD #CloudTips

Headline: 🐙 Day 1/10: Stop naming files "final_v2_real_final.txt"! Welcome to the World of Git. 📸 Post Content: Hello Connections! 👋 Welcome to Day 1 of the 10-Day Git & GitHub Challenge! If you have ever worked on a project and ended up with files named code_v1.py, code_v2.py, and code_final_I_swear.py, you desperately need Version Control. In the tech industry, whether you are a Developer, DevOps Engineer, or Data Scientist, you DO NOT make copies of files. You use Git. Git is like a magical Time Machine for your code. 🐱🐭 The Tom & Jerry Analogy (The Blueprint): --> Jerry (The Noob): Jerry is drawing a blueprint. Every time he makes a change, he makes a full photocopy. Soon, his desk is overflowing with 50 different blueprints. He gets confused and builds a house with the kitchen in the bathroom. --> Tom (The Pro): Tom draws on one blueprint. Every time he reaches a milestone, he puts it in a magical box (git add) and takes a snapshot with his magical camera (git commit). If he messes up tomorrow, he just restores a snapshot from yesterday. 🌍 Git vs GitHub (The Biggest Confusion): --> Git: The camera you use on your laptop to take snapshots of your code. (It works offline). --> GitHub: The online photo album (Cloud) where you upload those snapshots to share with your friends and team. 🔥 Today's Mini-Challenge: Let's initialize your first magical album! Create a folder and open your terminal in it. Turn it into a Git repository: git init Check the status: git status 👇 Key Commands: --> git init (Start tracking this folder) --> git status (Check what changed) Drop a 📸 in the comments if you initialized your first repo! Blog link: https://lnkd.in/gKKAMQyh #Git #GitHub #DevOps #Day1 #10DayChallenge #VersionControl #SoftwareEngineering #Coding #TechSkills

🚀 Hands-on with Jenkins CI Pipelines this week! Spent some time building and debugging pipelines while learning how CI systems actually work behind the scenes. Two small projects, but a lot of practical learning. 🔹 Project 1: My First Jenkins Pipeline Started with a simple pipeline to understand the basics of how Jenkins executes tasks. What I explored: ✅ Jenkins pipeline structure (pipeline → stages → steps) ✅ Running shell commands through Jenkins ✅ Debugging builds using Console Output Even a basic pipeline helps you understand how CI servers automate workflows. 🔹 Project 2: Multi-Stage, Multi-Agent Pipeline Next step was implementing a more realistic CI pipeline using Docker agents. Pipeline stages: ⚙️ Back-end Stage → Runs inside a Maven Docker container 🎨 Front-end Stage → Runs inside a Node Docker container Pipeline architecture looked like this: GitHub Repository ↓ Jenkins ↓ Docker Container (Maven) ↓ Docker Container (Node) Each stage spins up its own container environment, executes commands, and shuts down automatically. This ensures: 🔹 Isolated builds 🔹 No dependency conflicts 🔹 Reproducible environments 💡 Biggest takeaway: Most of the learning came from debugging failures -missing tools, plugin issues, path problems, Docker permissions, etc. That’s where the real DevOps understanding develops. 🛠 Tech Stack Used ⚡ Jenkins ⚡ Git ⚡ Docker ⚡ AWS EC2 (Free Tier) ⚡ Linux #DevOps #Jenkins #Docker #CICD #CloudComputing #AWS #LearningInPublic

🚀 Just finished the Docker course on Boot.dev! 🚀 I’m excited to share that I’ve learned the fundamentals of Docker—a key technology in modern DevOps and CI/CD pipelines. Docker makes it simple and fast to deploy new versions of code by packaging applications and their dependencies into preconfigured environments. This not only speeds up deployment, but also reduces overhead and eliminates the “it works on my machine” problem. Docker is a core part of the CI/CD (Continuous Integration/Continuous Deployment) process, enabling teams to deliver software quickly and reliably. Here’s a high-level overview of a typical CI/CD deployment process: The Deployment Process: 1. The developer (you) writes some new code 2. The developer commits the code to Git 3. The developer pushes a new branch to GitHub 4. The developer opens a pull request to the main branch 5. A teammate reviews the PR and approves it (if it looks good) 6. The developer merges the pull request 7. Upon merging, an automated script, perhaps a GitHub action, is started 8. The script builds the code (if it's a compiled language) 9. The script builds a new docker image with the latest program 10. The script pushes the new image to Docker Hub 11. The server that runs the containers, perhaps a Kubernetes cluster, is told there is a new version 12. The k8s cluster pulls down the latest image 13. The k8s cluster shuts down old containers as it spins up new containers of the latest image This process ensures that new features and fixes can be delivered to users quickly, safely, and consistently. image credit: Boot.dev Docker course #docker #cicd #devops #softwaredevelopment #bootdev #learning

🚀 𝗪𝗵𝗮𝘁 𝗔𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗛𝗮𝗽𝗽𝗲𝗻𝘀 𝗪𝗵𝗲𝗻 𝗬𝗼𝘂 𝗣𝘂𝘀𝗵 𝗖𝗼𝗱𝗲 𝘁𝗼 𝗚𝗶𝘁𝗛𝘂𝗯? Most beginners think “𝗴𝗶𝘁 𝗽𝘂𝘀𝗵” 𝗷𝘂𝘀𝘁 𝘂𝗽𝗹𝗼𝗮𝗱𝘀 𝗰𝗼𝗱𝗲. But in real DevOps environments… That single command can 𝘁𝗿𝗶𝗴𝗴𝗲𝗿 𝗮𝗻 𝗲𝗻𝘁𝗶𝗿𝗲 𝗮𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗼𝗻 𝗽𝗶𝗽𝗲𝗹𝗶𝗻𝗲. 💼 𝗜𝗻 𝗿𝗲𝗮𝗹 𝗰𝗼𝗺𝗽𝗮𝗻𝗶𝗲𝘀... When developers push code to GitHub, it often starts a 𝗖𝗜/𝗖𝗗 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄. 𝗧𝗵𝗮𝘁 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄 𝗺𝗮𝘆 𝗮𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗰𝗮𝗹𝗹𝘆: • Run automated tests • Build the application • Scan for vulnerabilities • Build Docker images • Deploy to staging or production So a simple 𝗽𝘂𝘀𝗵 𝗰𝗮𝗻 𝘁𝗿𝗶𝗴𝗴𝗲𝗿 an entire 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗱𝗲𝗹𝗶𝘃𝗲𝗿𝘆 𝗽𝗶𝗽𝗲𝗹𝗶𝗻𝗲. ⚙️ 𝗪𝗵𝗮𝘁 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗵𝗮𝗽𝗽𝗲𝗻𝘀 𝘀𝘁𝗲𝗽-𝗯𝘆-𝘀𝘁𝗲𝗽? 1️⃣ Developer writes code locally 2️⃣ Code is committed with git commit 3️⃣ Code is pushed to GitHub with git push 4️⃣ GitHub stores the new commit in the repository 5️⃣ Webhooks trigger CI tools (Jenkins, GitHub Actions, etc.) 6️⃣ CI pipeline starts build + tests 7️⃣ Artifacts are created (Docker image, binaries) 8️⃣ CD pipeline may deploy automatically This is how 𝗺𝗼𝗱𝗲𝗿𝗻 𝗗𝗲𝘃𝗢𝗽𝘀 𝘁𝗲𝗮𝗺𝘀 𝘀𝗵𝗶𝗽 𝗰𝗼𝗱𝗲 𝗺𝘂𝗹𝘁𝗶𝗽𝗹𝗲 𝘁𝗶𝗺𝗲𝘀 𝗽𝗲𝗿 𝗱𝗮𝘆. 🧠 𝗦𝗶𝗺𝗽𝗹𝗲 𝗮𝗻𝗮𝗹𝗼𝗴𝘆  • Think of GitHub like a switch that starts a factory machine.  • You press the switch (git push)  • And suddenly the factory starts:  • Code → Build → Test → Package → Deploy ❌ 𝗖𝗼𝗺𝗺𝗼𝗻 𝗺𝗶𝘀𝘁𝗮𝗸𝗲 𝗯𝗲𝗴𝗶𝗻𝗻𝗲𝗿𝘀 𝗺𝗮𝗸𝗲 They think: 𝗚𝗶𝘁𝗛𝘂𝗯 = 𝗼𝗻𝗹𝘆 𝗰𝗼𝗱𝗲 𝘀𝘁𝗼𝗿𝗮𝗴𝗲. ❌ 𝗡𝗼𝘁 𝘁𝗿𝘂𝗲. GitHub is also the 𝗲𝘃𝗲𝗻𝘁 𝘁𝗿𝗶𝗴𝗴𝗲𝗿 𝗳𝗼𝗿 𝗮𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗼𝗻 𝗽𝗶𝗽𝗲𝗹𝗶𝗻𝗲𝘀. 🎯 𝗜𝗳 𝘆𝗼𝘂 𝗿𝗲𝗺𝗲𝗺𝗯𝗲𝗿 𝗢𝗡𝗘 𝘁𝗵𝗶𝗻𝗴  • git push is not just uploading code.  • It can start the entire DevOps delivery pipeline. 💬 𝗛𝗼𝘄 𝗺𝗮𝗻𝘆 𝘁𝗶𝗺𝗲𝘀 𝗽𝗲𝗿 𝗱𝗮𝘆 𝗱𝗼𝗲𝘀 𝘆𝗼𝘂𝗿 𝘁𝗲𝗮𝗺 𝗽𝘂𝘀𝗵 𝗰𝗼𝗱𝗲? 𝗙𝗼𝗹𝗹𝗼𝘄 𝗼𝘂𝗿 𝗟𝗶𝗻𝗸𝗲𝗱𝗜𝗻 𝗣𝗮𝗴𝗲 𝗳𝗼𝗿 𝗱𝗮𝗶𝗹𝘆 𝗰𝗹𝗼𝘂𝗱 𝗰𝗹𝗮𝗿𝗶𝘁𝘆: https://lnkd.in/dN4JSkfH 𝗝𝗼𝗶𝗻 𝗼𝘂𝗿 𝗪𝗵𝗮𝘁𝘀𝗔𝗽𝗽 𝗖𝗹𝗼𝘂𝗱 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝘁𝘆: https://lnkd.in/dTJfEFyK 𝗪𝗲𝗯𝘀𝗶𝘁𝗲: www.vyomanant.com #DevOps #GitHub #CICD #Docker #Kubernetes #CloudComputing #DevOpsEngineer #LearnDevOps #VyomanantAcademy #Vyomanant