Irfan Jamadar

• Working as O365 administration and working on Microsoft Azure environments, involved in Azure configuring virtual machines, Storage accounts and Azure resource groups.
• Experience with Microsoft 365 and office 365, including Teams, SharePoint Online, OneDrive, and Exchange Online.
• Experience with cloud computing and Virtualization
• Administrator Azure AD users, groups, and devices,
• Deployment of Virtual Machines to Virtual Networks using Azure portal.
• Working Experience with Microsoft Azure Administrator like virtual machine scale set(VMSS) with load balancers, Virtual networks, & learning Docker and Kubernetes.
• Cloud Concepts: IaaS, PaaS, SaaS
• Automation: Basic knowledge of Azure DevOps, ARM Templates
• Version Control : Proficient in using Git for version control and collaboration on code repositories.
• Continuous Integration/Continuous Deployment (CI/CD) : Knowledge of Jenkins for setting up and managing CI/CD pipelines.

Project: DevOps Lifecycle Implementation for Abode Software

Role: DevOps Engineer (Capstone Project)
Description:

• Designed and implemented a comprehensive DevOps lifecycle for a product-based company to streamline development and deployment processes.
• Utilized configuration management tools to automate the installation of necessary software across multiple machines.
• Established a Git workflow to manage code changes efficiently, ensuring proper version control and collaboration.
• Configured automated CI/CD pipelines using Jenkins to trigger builds and tests upon code commits:
• Job1 (Build): Automated the build process to containerize the application using Docker, ensuring consistency across environments.
• Job2 (Test): Automated testing for commits to the develop branch, ensuring code quality before merging.
• Job3 (Prod): Automated deployment to production for commits to the master branch, enabling rapid and reliable releases.
• Containerized the application using Docker, with the Dockerfile configured to build automatically upon GitHub pushes. The application code was deployed to /var/www/html within the container.
• Integrated GitHub with Jenkins to trigger builds and tests based on branch-specific workflows:
• Commits to master triggered testing and deployment to production.
• Commits to develop triggered testing only, ensuring stability before production deployment.

Technologies Used:

• Configuration Management Tools (Ansible)
• Git and GitHub for version control
• Jenkins for CI/CD pipeline automation
• Docker for containerization
• Linux (file system management, scripting)