Automate Deployments with GitHub Actions and CI/CD

🚨 Attention @GitHub — We found a serious bug and you need to know. Today my team pushed commits to our main branch. Netlify deployed them. ✅ Commit hashes showed up in Netlify production logs. ✅ But GitHub commit history? Completely blank. ❌ The commits EXIST — Netlify's webhook received them with the correct SHAs (d5c89e1, 41c81dc, 7506412). But GitHub's own UI doesn't show them. This is a critical reliability issue. If your commit history doesn't reflect actual pushes, how can developers trust version control? → Not a force push issue. → Not a rebase. → Standard git push from multiple team members. → Webhook fires correctly, history doesn't update. We've reported this via GitHub Support — but I'm tagging this publicly because this could silently affect other teams who haven't noticed yet. @GitHub please investigate your event propagation pipeline between push events and the commit history UI. Have you or your team experienced this? Drop a comment. 👇 #GitHub #GitHubBug #DevTools #WebDevelopment #Git #Netlify #OpenSource #BugReport

Shipping faster starts with one integration. Connecting GitHub to Vercel takes less than 2 minutes, and it changes everything about how you share your work. Every pull request gets its own live preview URL. Automatically. No extra config, no manual deploys, no "can you send me the build?" messages. Here's what you unlock instantly: ⚡ Preview deployments on every PR, shareable with one link ✅ Stakeholders review real UI, not screenshots 🎯 Feedback loops cut from days to minutes 🔗 Production deploys triggered automatically on merge 🛡️ Zero risk of showing unfinished work on your main domain I use this on every project now. A designer, a client, or a PM can click a link and see exactly what the feature looks like, before it ships. No staging server. No "works on my machine." Just a URL. Have you tried Vercel preview deployments yet? What changed in your workflow when you did? #Vercel #GitHub #WebDevelopment #DeveloperExperience #DevOps

Sveltos v1.8.0 is out. Three new features, handful number of bug fixes, each targeting a specific operational gap. 1. 𝗚𝗶𝘁𝗢𝗽𝘀-𝗳𝗿𝗶𝗲𝗻𝗱𝗹𝘆 𝗸𝘂𝗯𝗲𝗰𝗼𝗻𝗳𝗶𝗴 𝗿𝗲𝗻𝗲𝘄𝗮𝗹 When Sveltos rotated a cluster's kubeconfig, it wrote a new key (`re-kubeconfig`) and updated `SveltosCluster.spec`. GitOps tools like Flux or ArgoCD saw this as live-state drift from the Git source. The fix is a new field: 𝘴𝘱𝘦𝘤:  𝘵𝘰𝘬𝘦𝘯𝘙𝘦𝘲𝘶𝘦𝘴𝘵𝘙𝘦𝘯𝘦𝘸𝘢𝘭𝘖𝘱𝘵𝘪𝘰𝘯:  𝘬𝘶𝘣𝘦𝘤𝘰𝘯𝘧𝘪𝘨𝘒𝘦𝘺𝘕𝘢𝘮𝘦: 𝘬𝘶𝘣𝘦𝘤𝘰𝘯𝘧𝘪𝘨 # 𝘴𝘢𝘮𝘦 Set 𝘬𝘶𝘣𝘦𝘤𝘰𝘯𝘧𝘪𝘨𝘒𝘦𝘺𝘕𝘢𝘮𝘦 to the existing key name and Sveltos overwrites the Secret in-place, skipping the spec update. Live state and Git stay aligned 2. 𝗦𝗸𝗶𝗽 𝗻𝗮𝗺𝗲𝘀𝗽𝗮𝗰𝗲 𝗰𝗿𝗲𝗮𝘁𝗶𝗼𝗻 𝗳𝗼𝗿 𝗿𝗲𝘀𝘁𝗿𝗶𝗰𝘁𝗲𝗱 𝗥𝗕𝗔𝗖 In multi-tenant clusters where Sveltos operates without cluster-wide Namespace permissions, the pre-flight namespace check would fail even when the namespace already existed. 𝘚𝘬𝘪𝘱𝘕𝘢𝘮𝘦𝘴𝘱𝘢𝘤𝘦𝘊𝘳𝘦𝘢𝘵𝘪𝘰𝘯: 𝘵𝘳𝘶𝘦 on 𝘗𝘰𝘭𝘪𝘤𝘺𝘙𝘦𝘧s and 𝘒𝘶𝘴𝘵𝘰𝘮𝘪𝘻𝘢𝘵𝘪𝘰𝘯𝘙𝘦𝘧𝘴 bypasses that check and deploys directly into pre-provisioned namespaces. 3. 𝗡𝗮𝘁𝗶𝘃𝗲 𝗛𝗲𝗹𝗺 𝘁𝗲𝘀𝘁 𝗲𝘅𝗲𝗰𝘂𝘁𝗶𝗼𝗻 Helm charts ship with test hooks that authors write precisely to validate a deployment. With 𝘳𝘶𝘯𝘛𝘦𝘴𝘵𝘴: 𝘵𝘳𝘶𝘦 in the chart spec, Sveltos runs those hooks automatically after each successful install or upgrade. Failures surface as deployment failures in ClusterSummary status. 𝗕𝘂𝗴 𝗳𝗶𝘅𝗲𝘀 𝘄𝗼𝗿𝘁𝗵 𝗻𝗼𝘁𝗶𝗻𝗴 Modifying Helm patches no longer goes undetected when chart version and values are unchanged. Sveltos now tracks a hash of the patch set. Failure messages on Helm releases are no longer overwritten before persisting. And manually deleting a ClusterSummary while a cluster is mid-update no longer causes a reconciliation deadlock. Full changelog: https://lnkd.in/d65DAXuA #Kubernetes #MultiCluster #GitOps #PlatformEngineering #Sveltos

#100DaysOfDevOps - Day Forty - Six Today I continued working on the GitHub Actions version of my CI pipeline. The focus was on moving from the workflow skeleton into actual execution, one stage at a time, while testing and troubleshooting along the way. What I worked on today: ✅ created the .github/workflows/ci.yaml file ✅ pushed it to GitHub and confirmed the workflow was triggered ✅ verified that the checkout stage worked ✅ observed how GitHub Actions provisions a runner automatically ✅ added the backend test stage ✅ set up Python on the runner ✅ installed pip ✅ confirmed the backend test/lint stage ran successfully After that, I moved into the image build stage and started setting up: Docker-related steps GitHub secrets for Docker authentication environment variables for image names and tags That part came with multiple errors, including: wrong field names wrong action version invalid Docker tag formatting mismatched secret references And honestly, I’m glad it happened that way. Because one thing this journey keeps reinforcing is: CI/CD is not learned by only watching clean demos. It is learned by writing, testing, failing, correcting, and understanding why the workflow failed. So even though the image build stage is still being resolved, today still felt like strong progress because the earlier stages are now working, and the workflow is taking shape properly. Big takeaway: The deeper skill is not avoiding errors, it is learning how to read them and move forward with clarity. YouTube Video Link: https://lnkd.in/eDVKJz8d #DevOps #100DaysOfDevOps #GitHubActions #CICD #ContinuousIntegration #Docker #Automation #GitHub #YAML #PlatformEngineering #CloudEngineering #LearningInPublic #TechdotSam

Nested Contianers - The penultimate scene! In the last post - https://lnkd.in/ewJBedhd - we have seen how Kubedock saved the world, even though by faking Docker APIs and make them available to other processes, So they think "I’m talking to Docker" while they actually talk to Kubedock. Great Idea, i'm still amazed how would someone think of this, but "Yes" we all did nice fake things from mockup services "microcks" all the way to faking kubernetes "KWOK". Before we explore another important option - user namespaces [ https://lnkd.in/egqMy6Mh ] - to run nested containers in OpenShift DevSpaces we have to recall the following : 1 - We - the developers - want an automated unit and integration testing experience inside our devworkspaces. 2 - Unit testing in most frameworks - like quarkus and spring boot - require docker to be available to start test containers. 3 - Again, we don't want to deal with docker socket and how to configure Podman to expose a Docker-compatible socket, I just want my unit testing use cases to run. 4 - Yet, We from time to time would like to run some other containers for experimentation and not only for testing scenarios, so please don't limit me to unit and integration testing scenarios. Because of the above 4 reasons - and some more, we started with Kuedock and we - the development community - might favor this approach over the user namesapce. In the next post we will discuss in details the user namespace option with a quick demo to show how it works. You can get yourseld familiar with the concept of user namespace in DevSpaces documentation https://lnkd.in/e-G3R3aQ Finally, look at the beauty of how Kubedock was integrated into universal developer image UDI in the official dockerfile on redhat catalog: https://lnkd.in/eK2u5-yK #redhat #openshift #devspaces #kubedock #nested #containers

I've been contributing to GitLab's open-source codebase through CodePath's AI Corps x GitLab program (AI 301), and two of my merge requests have already been merged into production. The program pairs contributors with GitLab engineers who guide you through the process and are there if you need help working through real issues. My contributions so far include frontend lint and code quality fixes across usage billing components and a Vue component naming lint fix. Beyond the code itself, I picked up a lot from setting up GDK-in-a-box, navigating a massive monorepo, writing targeted specs after each fix, and working through the review process with maintainers. Working on more issues now. If you're looking to get into open-source contribution, the CodePath x GitLab program is a solid way in. #OpenSource #GitLab #SoftwareEngineering #CodePath

Most developers use Docker & Kubernetes daily… but only know ~30% of the commands that actually matter in production. That’s why debugging takes hours. That’s why deployments feel “random.” Here’s a no-fluff cheat sheet of the commands you’ll actually use— from building images → debugging pods → fixing production issues fast. If you work with containers, this is worth bookmarking. #ArchitectMindset #Docker #Kubernetes #DevOps #CloudNative #Microservices #SoftwareEngineering #BackendDevelopment #Containers #K8s #TechTips

🛡️ "In Git We Trust" We're kicking off the useblocks X-as-Code Webinar Series - in collaboration with GitHub - next week, April 22nd. Still managing engineering artefacts outside Git? Then this is for you. The shift toward X-as-Code is accelerating, especially in safety-critical industries. And it starts with the fundamentals. 🚀 The Series Premiere: Arnaud Riess, a pioneer of X-as-Code at a global automotive Tier-1, opens the series with: "X-as-Code Foundations - In Git We Trust" What we’re covering: 🔹 Why document-centric engineering is failing to scale. 🔹 Treating requirements, architecture, and compliance as version-controlled assets. 🔹 Why this approach is the "secret sauce" for AI readiness. 🔹 Leveraging open-source foundations like Sphinx-Needs. No prior experience required. Structured content + live Q&A. All registrants receive slides and recording. 📅 When: April 22nd | 4 PM CET 📍 Where: Live Webinar (+ Recording for all registrants) Registration link in the first comment. #useblocks #XasCode #SpecDrivenDevelopment #GitHub #SafetyCritical #OpenSource #SphinxNeeds #AutomotiveSoftware

𝗜 𝗷𝘂𝘀𝘁 𝘀𝗽𝗲𝗻𝘁 𝟱 𝗵𝗼𝘂𝗿𝘀 𝗱𝗲𝗯𝘂𝗴𝗴𝗶𝗻𝗴 𝗧𝗲𝗿𝗿𝗮𝗳𝗼𝗿𝗺. No progress. Just errors. But here’s the truth: That was the progress. Every broken config, every cryptic error message, every failed apply - it forced me to actually understand what was going on. Not copy. Not guess. Understand. Tutorials show you the “happy path.” Debugging teaches you reality. If you’re constantly breaking things, you’re not doing it wrong - you’re learning the part most people skip. Break it. Fix it. Repeat. That’s where the real skill is built. CoderCo #terraform #DevOps #debugging #progress

Mono-repos introduce complexity not just in code, but in collaboration. This month's in-person GerritMeets explores: Gerrit’s code-owners plugin in practice advanced Owners plugin capabilities strategies to scale code review across large teams 📍 Munich 👉 Save your spot: https://lnkd.in/emdrHUPh #monorepos #Git #DevOps #Gerrit #GerritMeets