THUMMA SAI KIRAN
Devops/Build and Release Engineer Email: ********@*****.***
Sunnyvale, CA – 94086 Cell Phone:669-***-****
Work Experience:
Overall 3years of experience as a Build and Release Engineer and Devops Engineer.
Experience in implementing Organization DevOps strategy in various Linux and windows servers which might be adapting any cloud strategies.
Having sound knowledge in setting up the servers on different flavors of Linux like Redhat, CentOS, Ubuntu, Solaris and windows.
Excellent understanding of SDLC Methodologies like Agile Methodology, Waterfall.
Strong experience in Build and Release DevOps Engineering in automating, build, deploying, and releasing of code from one environment to another environment.
Extensively used build utilities like Maven, ANT for building of jar, war, bar and ear files.
Strong knowledge of DNS, DHCP and IP Addressing. Installation and configuration of various services like DNS, DHCP, NFS, Send mail, Apache Web Server, SSH, HTTP, RPM package management. Experience in administering Active Directory and group policies.
Hands on experience of Build & Deployment phase and usage of Continuous Integration (CI/CD) tools, build configuration, change history for releases, Maintenance of build system, automation & smoke test processes, managing, configuring, and maintaining source control management systems.
Extensively used build utilities like Maven, ANT for building of jar, war and ear files.
Extensively used dpkg services to install different packages and services on the Ubuntu based debian servers.
Automated processes with custom built Python & Shell scripts.
Experience in using Version Control Systems GIT as repositories for saving source code.
Experience in using bug tracking tools for testing the source code such as JIRA
Exposed to all aspects of software development life cycle (SDLC) such as Analysis, Planning, Developing, Testing, implementing and Post-production analysis of the projects.
Expert level knowledge on Amazon EC2.
Experience in running web scale services on Amazon Web Services.
Used Monitoring Tools such as Splunk, for Resource Monitoring/Network Monitoring/Log Trace Monitoring.
Knowledge on Deploying Couch base, Tomcat and Elastic search clusters using Docker.
Application Deployments & Environment configuration using Chef.
Expert in supporting and installing third party software on workstations.
Technical Skills:
Version Controlling Tools
Subversion, GIT, Stash, Source Tree
CI/CD Tools
ANT, Maven, Jenkins, Chef, Docker, AWS, RunDeck
Tools
Nexus, Artifactory, New Relic, Kubernetes, SonarQube
Scripting Languages
Unix Shell scripting, Python, Powershell
Operating Systems
Centos, Ubuntu, Windows, UNIX, RedHat, Ubuntu
Web/Application Servers
Apache Tomcat
Bug Tracking Tools
JIRA, Splunk, Confluence
Education:
Master’s California State University, Fullerton Jan2015 – May2016
Professional Experience:
Tennant, Minneapolis, MN
Role: Devops/Build and Deploy Engineer Feb 2017 -Till Date
Responsibilities:
Migration from Linux servers to windows 2008 R2 server.
Using PowerShell scripting language to write scripts for automation build.
Experience in using Stash for saving scripts as repositories.
Using Confluence for the flow of project documentation.
Building the Jenkins pipeline for Build Automation, CI/CD.
Using Maven as Build Tools on Java Project for the development build artifacts.
Jenkins Pipeline being built for Dev, Qa, Uat and Prod.
Creating a Cluster for Uat and Production Deployments.
Testing the Jenkins process according the build the artifacts and deployments.
Configuring the Jenkins as per the windows servers and the injecting the property files.
PowerShell scripting to write the deployment scripts.
Documentation of the process flow for further use these scripts for updating the configurations and components.
Environment: Ant, Maven, PowerShell, Apache Tomcat, GIT, Stash, Confluence and Jenkins.
Kronsys, North Carolina, USA Aug2016 – Jan-2017
Role: Build and Release Engineer/DevOps Engineer
Responsibilities:
Performed software Configuration/Release management activities for different java applications.
Performed Branching, Merging, Tagging activities on Version Control Tools: SVN, GIT.
Addressed software configuration management issues in coordination with the development team.
Maintained and updated source code repositories on a regular basis.
We have used Jenkins continuous integration system to automate builds.
Scripting in multiple languages on Unix, Linux and Windows-Python, Shell Scrip etc.
Troubleshooting the build issues during the build process by Jenkins.
Installed and configured Red Hat Linux, established and scheduled activities in test and production environments.
Automate regular tasks using Python Scripting.
Worked on Nexus for deploying artifacts and used JIRA as a ticketing tool.
Deployed the java applications into web application servers like Nexus.
Build automation and build pipe development using Jenkins and Maven.
Worked extensively with MAVEN build tools for writing build.xml and pom.xml files respectively.
Implemented rapid-provisioning and life-cycle management for Ubuntu Linux using Amazon EC2, Chef, and custom Ruby/Bash Scripts.
Automated the cloud deployments using chef, Python and AWS cloud formation templates.
Environment: Chef, AWS EC2, MAVEN, NEXUS, GIT, SVN, JENKINS, PYTHON
Project: Airdata, Android Application (Final Project at Masters) Jan 2015- May 2016
Role: Support Engineer
Responsibilities:
Documentation process about the project using Agile methodologies, CMMI, IEEE Rules.
Saving the source code in Git Repositories.
Build Automation for test case and compiling the source code.
Build the structure for the source code.
Using Jenkins continuous integration and continuous deployment.
Developer of a scrum team would fetch the code to Git repositories.
Used Git for cloning the source code and pushing it to remote repositories.
Configuration and building a platform such any Linux server.
I have written Scripts for POM.XML for Maven build tool.
I have knowledge on python scripting which I have used in writing scripts in Jenkins.
Documentation part for the final project report.
We have followed Agile process to complete the project.
Environment: Ubuntu, Agile, Python, Maven, Jenkins
Bristlecone, Pune, India Aug 2013 – Nov 2014
Role: Build and Release Engineer
Responsibilities:
Release Engineer for a team that involved different development teams and multiple simultaneous software releases.
Developed and implemented Software Release Management strategies for various applications according to the agile process.
Participated in weekly release meetings with Technology stakeholders to identify and mitigate potential risks associated with the releases.
Imported and managed multiple corporate applications into Subversion (SVN).
Involved in creating new Build Definitions, creating and updating Build Process Templates for new releases and new requirements.
Responsible for maintaining MS Build and PowerShell files for build and automation of .Net and C Sharp applications.
Involved in all projects that move to production and work closely with the Data Center, Development, Quality Assurance and Management teams to ensure cross communication and confirmed approval of all production changes
Developed build and deployment scripts using ANT/Maven as build tools and Jenkins as automation tool to move from one environment to other environments.
Built and Deployed Java/J2EE to a web application server in an Agile continuous integration environment and also automated the whole process.
Created and maintained the Shell/Perl deployment scripts for web application servers.
Developed Perl and shell scripts for automation of the build and release process.
Involved in tweaking the existing ANT files in case of errors or changes in the project requirements.
Perform periodic system audits on all environments to ensure that only controlled versions of software reside all environments.
Responsible for the development and maintenance of processes and associated scripts/tools for automated build, testing and deployment of the products to various developments.
Managed Maven project dependencies by creating parent-child relationships between projects.
Jenkins is used as a continuous integration tool for automation of daily process.
Installed, Configured and Managed Nexus repository manager for dependency management between different projects.
Integrated JIRA and Subversion using Pre-commit hooks to ensure the process is followed and automated JIRA tasks using JIRA CLI.
Worked as a production support in a large environment with configuration management tools like Chef.
Worked with performance monitoring tools like New Relic.
Experience on python scripting for Jenkins integration.
Environment: ANT, Subversion, Maven, Jenkins, Web Logic, JIRA, JAVA/J2EE, Shell Script, Nexus, Chef.