Quadrant Systems Pty Ltd’s Post

🚀 CI/CD on Kubernetes with Jenkins In this workflow, code committed to GitLab is automatically built by Jenkins, the resulting image is pushed to a container registry, and then deployed to the Kubernetes cluster, where the web service becomes accessible to end users. 🌐 #jenkins #devops #automation #deployment #kubernetes

#JENKINS# #CICD# Jenkins is the leading open-source automation server for building, testing, and deploying software. It is a critical tool for implementing Continuous Integration (CI) and Continuous Delivery (CD) in a DevOps workflow. Key Features: Automation: Automates the entire software delivery pipeline. Extensibility: Massive ecosystem of plugins for integrating with almost any tool.

Day 75 – #100DaysOfDevOps #KodeKloud Situation: The Nautilus DevOps team recently set up a new Jenkins server in Stratos Datacenter to handle CI/CD pipelines and automation tasks. To execute jobs across different application servers, we needed to add all app servers as slave (build agent) nodes in Jenkins. Task: Configure App Server 1, 2, and 3 as SSH build agents in Jenkins with proper labels and directories, ensuring all nodes are online and ready for job execution. Action: 🔹 Step 1: Access Jenkins UI Logged in using credentials: admin / Adm!n321. Verified Jenkins master was up and running.   🔹 Step 2: Install Required Plugin Installed SSH Build Agents Plugin to enable node connections. Restarted Jenkins and refreshed UI.   🔹 Step 3: Add Nodes Navigated to Manage Jenkins → Nodes → New Node. Added the following: App_server_1: Label stapp01, Remote root /home/tony/jenkins App_server_2: Label stapp02, Remote root /home/steve/jenkins App_server_3: Label stapp03, Remote root /home/banner/jenkins   Configured SSH authentication for each node using the respective app server credentials.   🔹 Step 4: Test Node Connections Verified all nodes showed “Connected” and “Online” status in the Jenkins dashboard. Ran a quick test build to confirm remote job execution worked correctly. Result: 1) ✅ All three app servers were successfully added as Jenkins build agents. 2) ✅ Nodes were online, correctly labeled, and ready for distributed builds. 3) ✅ This setup will allow Jenkins to execute jobs on specific environments efficiently. Learning: Configuring distributed Jenkins nodes improves scalability and isolation in CI/CD pipelines, enabling better workload management across multiple servers. 👉 Here’s the link to join the challenge: https://lnkd.in/g4wnpsF2 #Day75 #KodeKloudEngineer #DevOps #Jenkins #CICD #Automation #LearningByDoing #DevOpsChallenge #ContinuousLearning 

As part of integrating Jenkins into the CI/CD pipelines, I set up user-based access control — ensuring developers have the right permissions while keeping the system secure. This involved enabling project-based matrix authorization, assigning least-privilege access, and verifying role-based visibility across jobs. Excited to keep building more reliable and secure automation workflows! https://lnkd.in/eSbzGptR #Jenkins #CICD #DevOps #Automation #Pipeline #Security #AccessControl #Engineering #ContinuousIntegration #ContinuousDelivery #TechJourney #LearningByDoing

In modern software development, speed and reliability are everything. Continuous Integration and Continuous Deployment (CI/CD) pipelines help teams deliver updates faster, minimise manual intervention, and ensure consistent quality across releases. - Jenkins offers deep customisation, plugin flexibility, and on-prem control, ideal for teams needing full autonomy. - GitHub Actions provides cloud-native simplicity, seamless GitHub integration, and effortless scalability. - Each tool has its strengths. Jenkins shines in complex, multi-environment setups, while GitHub Actions excels at quick automation and collaboration. Whether you're managing enterprise workloads or open-source projects, mastering both platforms can give your team the agility to ship better software, faster. #CICD #DevOps #Jenkins #GitHubActions #Automation #SoftwareDevelopment #DevOpsEngineering

DevOps with n8n + Jenkins Jenkins has long been tool for CI/CD that used for building, testing, and deploying software. But software delivery doesn’t end when code is deployed. Teams need notifications, reporting, approvals, release notes, tickets update and integrations with the tools they use every day. That’s where n8n comes in. By connecting Jenkins with n8n, we bridge the gap between technical pipelines and business workflows. Jenkins handles the heavy lifting of code builds and deployments. n8n automates what happens around it. Updating Jira tickets, sending release notes to Slack, notifying clients, or logging details into Confluence. The result? 🔹 Faster delivery cycles 🔹 Smoother collaboration across tech and business teams 🔹 Less manual work, more focus on what matters Together, Jenkins and n8n create a seamless flow from code commit to communication and visibility. #devOps #n8n #jenkins #jira #cicd #tech

Mainframes are not legacy — they’re evolving. ⚙️ Discover how integrating DevOps, Git, and CI/CD pipelines with mainframe systems enables faster delivery, improved collaboration, and modern software practices. It’s time to bridge the gap between traditional reliability and modern agility. #DigitalTransformation #MainframeDevOps #EnterpriseIT #CICD #Innovation #SRUniversity #CSAI #SRU

Just automated our entire deployment process - here's what changed: Before: ❌ 3-hour manual deployments every Friday ❌ 2-3 deployment failures per month ❌ Weekend hotfixes when things broke After: ✅ 15-minute automated deployments ✅ Zero failed deployments in 3 months ✅ Developers can deploy anytime with confidence The game-changer? A simple CI/CD pipeline with these 4 stages: 1. Automated testing (unit + integration) 2. Security scanning (SAST + dependency check) 3. Blue-green deployment to staging 4. Automated promotion to production Tools used: Jenkins, Docker, Terraform, and AWS The best part? This wasn't a complex enterprise solution - just good DevOps fundamentals applied consistently. What's been your biggest automation win recently?

Robert Forbes talked to IT Brew about the importance of strong change-management in software development platforms and brining security and DevOps teams closer together. Read the article: https://lnkd.in/g8f-SbQM

Before I release the documentation tomorrow I'm going to break down 1 of the types in the Sonatype Nexus Artifact repository manager, although it has 3 types - Proxy • Hosted • Group. As a teaser I'll share my favorite type and you can read about the others in the article I publish. GROUP TYPE - This is my favorite type. It basically allows you to combine multiple repositories and even other repository groups into a single repository, and this means that Nexus users, developers, developer teams can use a single URL for there application which will give them access to multiple repositories at once instead of working with separate URLs for each repository. Nexus Administrators (DevOps Engineers for example) can configure and add repositories to a group and then Nexus users can use the URL of that group instead of maintaining the repository endpoints of individual repositories (like maven-proxy, maven-hosted, and maven-snapshots) ADVANTAGE: You can give developers a single endpoint to maintain. #DevOps #TWNDevOps #ArtifactManagement #Nexus