The DevOps Tools Engineer 2.0 exam from Linux Professional Institute (LPI) dedicates the entire objective 701.3 to Source Code Management, with #Git front & center! Dive into this new episode of the #DevOps series, by Fabian Thorns and Uirá Ribeiro, to learn why #Git matters: https://lpi.org/dl72 #SCM #DevOps #Git #VersionControl #opensource #FOSS #SoftwareDevelopment
Linux Professional Institute's DevOps Tools Engineer Exam Focus on Git SCM
More Relevant Posts
-
Day 05 of 30 Not every day is about big deployments. Some days are about keeping everything clean, organized and moving smoothly. Here is what I worked on: 🌐 Domain Update — Updated domain names and base URL environment variables across dev and production environments to reflect the new URLs correctly 📂 CI File Segregation — Split CI configuration files for the main app and other deployment into separate files with single repository. This makes each deployment independent, easier to manage and less risky to touch 🐳 Docker Image Cleanup — Verified GitLab registry cleanup and updated CI files to build and push Docker images with branch specific tags only — no more unnecessary images piling up in the registry 🚀 New Service Deployed — Set up complete GitLab CI configuration for a new API service and deployed it successfully to the dev environment 🔀 Code Reviews — Reviewed and merged MRs to keep the team unblocked The CI file segregation was the most useful thing today. When one big CI file handles everything, a small mistake can break all deployments. Splitting it gives you better control and reduces risk. Clean pipelines and clean registries are just as important as building new things. #DevOps #GitLabCI #Docker #CICD #DockerRegistry #Linux #DevOpsEngineer
To view or add a comment, sign in
-
📌 Continuing my DevOps Journey — this time with Git & GitHub! Git is the backbone of every modern development workflow. No Git = no DevOps. Here's what I covered: ✅ How Git works — Working Directory → Staging → Local Repo → GitHub ✅ Core commands — init, add, commit, push, pull, log, status ✅ Branching & Merging — and handling conflicts ✅ Stash, Reset & Revert — undoing changes the right way ✅ Tags, Clone & .gitignore ✅ Pull Requests — reviewing before merging Every DevOps pipeline starts with a git push. Now I actually understand what happens after that. 🚀 #DevOps #docker #linux #Git #GitHub #VersionControl #CloudEngineering #cheatsheet
To view or add a comment, sign in
-
-
🚀 Jenkins + GitHub Integration (CI/CD Basics) Documented a complete setup of integrating Jenkins with GitHub covering: ✔ Git Pull using pipeline ✔ Webhook-based auto trigger ✔ Secure Git Push from Jenkins Also explored the difference between credentialsId and withCredentials — a small concept but very important in real pipelines. 📊 Sharing my step-by-step PPT for reference 👇 #DevOps #Jenkins #GitHub #CICD #LearningInPublic
To view or add a comment, sign in
-
Recently I worked on CI/CD pipeline project to understand how automated deployments actually work in practice. This was my first time practically implementing a CI/CD workflow, and it helped me understand how different tools integrate together. Instead of only learning the tools individually, I tried connecting them together in a small working setup. 🔹 Server Side Configuration • Used Ansible to configure the target Linux server • Installed Docker and Docker Compose using automation • Prepared the server environment for running containers • Ensured the server was ready for automated deployments 🔹 CI/CD Pipeline • Code pushed to GitHub • GitHub webhook triggers Jenkins pipeline • Jenkins pulls the latest code from the repository • Pipeline deploys the application using Docker Compose • Application runs inside an Nginx container 🔹 What I Learned • How a CI/CD pipeline works end-to-end • How GitHub webhooks trigger Jenkins pipelines • Using Ansible for server configuration and automation • Deploying containers using Docker Compose • Connecting multiple DevOps tools in a simple workflow Tech Stack: GitHub | Jenkins | Ansible | Docker | Docker Compose | Nginx | Linux This was a small but useful learning project that helped me understand how these tools work together in a real workflow. #DevOps #CICD #Jenkins #Docker #Nginx #LearningJourney #Infrastructure #SRE #Platform
To view or add a comment, sign in
-
-
⚡ DevOps Shortcuts I Use Daily (and can’t live without): 💻 Linux Terminal Ctrl + C → Stop current process Ctrl + Z → Pause process Ctrl + R → Search command history !! → Repeat last command 🐳 Docker docker ps → List running containers docker images → List images docker logs -f → Live logs docker exec -it /bin/bash → Access container ☸️ Kubernetes (kubectl) kubectl get pods → List pods kubectl describe pod → Detailed info kubectl logs → View logs kubectl apply -f → Deploy config 🌿 Git git status → Check changes git log --oneline → Compact history git checkout -b → New branch git pull origin main → Sync code Small shortcuts, big productivity boost 🚀 What are your go-to DevOps commands? #DevOps #Linux #Docker #Kubernetes #Git #Productivity #TechTips
To view or add a comment, sign in
-
Starting your DevOps journey in 2026? Here is a roadmap that actually works👇 Start by spending the first 3 months building strong foundations: - Linux fundamentals - Git - Shell scripting - Docker Once your basics are clear, spend the next three months focusing on Kubernetes. After that, move into platform engineering and start working with real-world tools and workflows. Finally, pick advanced topics such as Terraform, Istio, and MLOps Here is the detailed guide for the 2026 DevOps roadmap. 𝐒𝐭𝐚𝐫𝐭 𝐋𝐞𝐚𝐫𝐧𝐢𝐧𝐠: https://lnkd.in/eE7EJeD 𝗡𝗼𝘁𝗲: Don’t try to learn everything at once. Go deep into one layer, then move to the next. #devops #devopsroadmap
To view or add a comment, sign in
-
-
Episode 4 of our DevOps Tools Engineer 2.0 Introduction series explores how #Git serves as the backbone of modern software development, #opensource collaboration, and #DevOps workflows. 🛠️ Learn more about the updated DevOps exam’s objective 701.3 (Source Code Management) from Fabian Thorns and Uirá Ribeiro, along with external resources: https://lpi.org/dl72 Linux Professional Institute (LPI) #SCM #DevOps #Git #VersionControl #opensource #FOSS #SoftwareDevelopment
To view or add a comment, sign in
-
-
Episode 4 of our DevOps Tools Engineer 2.0 Introduction series explores how #Git serves as the backbone of modern software development, #opensource collaboration, and #DevOps workflows. 🛠️ Learn more about the updated DevOps exam’s objective 701.3 (Source Code Management) from Fabian Thorns and Uirá Ribeiro, along with external resources: https://lpi.org/dl72 Linux Professional Institute (LPI) #SCM #DevOps #Git #VersionControl #opensource #FOSS #SoftwareDevelopment
To view or add a comment, sign in
-
-
Git Commands Every DevOps Engineer Should Know! Here's a visual guide to some essential Git commands that power your daily workflows: 1. git commit - Saves your changes with a message 2. git branch feature - Creates a new branch called "feature" 3. git checkout feature - Switches to the feature branch 4. git checkout main - Switches back to the main branch 5. git merge feature - Merges feature branch into main (Fast-forward!) 6. git revert HEAD - Undoes the last commit safely 7. git rebase main - Replays commits on top of another branch 8. git reset HEAD~1 - Moves the branch pointer back 9. git cherry-pick main - Applies a specific commit to current branch 10. git log - Shows the commit history with author and timestamps The visual Git graph shows how branches split, merge, and evolve. Understanding these commands helps you manage code efficiently in any DevOps pipeline. Which Git command do you use the most? #DevOps #Git #VersionControl #CI_CD #CloudNative #Linux #TechLearning
To view or add a comment, sign in
-
𝗗𝗮𝘆 𝟮𝟮 𝗼𝗳 𝗺𝘆 𝗗𝗲𝘃𝗢𝗽𝘀 𝗝𝗼𝘂𝗿𝗻𝗲𝘆 💻 Bringing code to life — cloned a Git repository to create a working copy for development 📥 𝗧𝗮𝘀𝗸: Clone Git Repository on Storage Server 𝗪𝗵𝗮𝘁 𝗜 𝗹𝗲𝗮𝗿𝗻𝗲𝗱 𝘁𝗼𝗱𝗮𝘆: • Difference between bare repository and working repository • How `git clone` creates a local working copy • Cloning repositories from local paths (not just GitHub) • Importance of using correct user permissions • Safe handling of shared repositories in production environments 𝗪𝗵𝗮𝘁 𝗜 𝗯𝘂𝗶𝗹𝘁 / 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗲𝗱: • Logged into Storage Server (`ststor01`) as `natasha` • Verified existence of repository `/opt/games.git` • Created destination directory `/usr/src/kodekloudrepos` • Cloned repository using `git clone /opt/games.git` • Verified working copy using `git status` 𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲𝘀: • Understanding local path-based cloning • Ensuring no permission or structure changes were made • Being careful to use the correct user (`natasha`) 𝗙𝗶𝘅 / 𝗟𝗲𝗮𝗿𝗻𝗶𝗻𝗴: • Learned that cloning from local repositories works the same as remote • Understood importance of maintaining repository integrity • Gained clarity on how working copies are used in development 𝗞𝗲𝘆 𝗧𝗮𝗸𝗲𝗮𝘄𝗮𝘆: Cloning is where development begins — it bridges the gap between a central repository and actual coding work. This felt like a real-world Git workflow setup 🚀 Do you mostly clone from local repos, GitHub, or enterprise tools like GitLab/Bitbucket? #Day22 #DevOps #Git #VersionControl #Linux #Automation #CloudComputing #AWS #DevOpsJourney #LearningInPublic #100DaysOfDevOps
To view or add a comment, sign in
-
Explore related topics
Explore content categories
- Career
- Productivity
- Finance
- Soft Skills & Emotional Intelligence
- Project Management
- Education
- Technology
- Leadership
- Ecommerce
- User Experience
- Recruitment & HR
- Customer Experience
- Real Estate
- Marketing
- Sales
- Retail & Merchandising
- Science
- Supply Chain Management
- Future Of Work
- Consulting
- Writing
- Economics
- Artificial Intelligence
- Employee Experience
- Workplace Trends
- Fundraising
- Networking
- Corporate Social Responsibility
- Negotiation
- Communication
- Engineering
- Hospitality & Tourism
- Business Strategy
- Change Management
- Organizational Culture
- Design
- Innovation
- Event Planning
- Training & Development