1. Email id: buildandrelease.scm@gmail.com
Email id: varra.reddy@infinite.com
Kishore Reddy Ph No: +91 –9676201571
PROFESSIONAL SUMMARY
 Having 6.2 years of IT experience in Configuration Management using Ansible, Chef and
Puppet. Version control system, Change Management and Build Engineering using Rational
Clear Case, Git and Subversion.
 Good experience in using Build Automation tools like Maven, ANT and Jenkins.
 Good experience as a DevOps using cloud services like Amazon EC2, OpenStack.
 Managed the Servers setup in Openstack and automated through Ansible for the project
Requirement.
 Experience practicing agile methodologies.
 Quick learner and adaptive to new challenging technological environments.
 Provide assistance to clients with the implementation of configuration management, release
management and process creation and control through the use of Ansible.
 Worked on different Operating Systems Microsoft Windows 98/NT/2K/XP, Microsoft Windows
Server 2003, RedHat Linux 6.5 and Ubuntu14.04.
 Worked as a devops engineer to maintain communication between team to automate the code in
Ansible.
 Customer focused, organized, detail oriented with the ability to meet deadlines.
 Excellent problem solving, analytical, communication skills and able to effectively manage
time and prioritize multiple projects.
 Good experience in writing shell and python scripts for build automation purpose and able to
call shell and python scripts in Ansible playbooks.
 Have used Docker services for containerization of packages between virtual machines and
hosts.
 Experienced in planning, deployment and administration of Ansible on LINIX platforms.
 Proficient with the installations and configuration of Ansible on UNIX (Linux) Servers.
 Created and implemented CM plans to include branching, bug tracking, release planning and
requirement planning strategies.
 Well Proficient in Validating Playbooks, Roles in Ansible.
 Expertise in deployment of applications in Tomcat and JBOSS_FSW servers.
 Executing builds and troubleshooting builds, Interaction with development and QA teams.
 Handling build, deployment and release activities for multiple projects.
 Good understanding about branching strategies, merging and taking regular backups of the
source code.
 Continuous Integration through Jenkins.
 Performed and Tested Bidirectional Migration in between SVN-GIT By using SubGit.
 Proficient with the installation, configuration and usage of Clear Vision Migrate2Svn,
Regarding Migration from CC-SVN and SVN-GIT on windows servers.
 Good Experience in writing Batch script for Migration of source code from SVN-GIT.

2.  Well Expertise in Installation, Configuration and usage of SVN Mirror for Migration from
SVN-GIT.
 Experience in using Bug/Defect tracking tools like Atlassian Jira.
 Good experience in code coverage tool like Sonar.
 Well Expertise in Preparing Test Cases for SIT Environment.
 Having good Experience on Mavenused to build latest check-in of the code.
 Experienced in using Atlassian Stash (bit bucket) as a Repository management tool.
 Experienced in planning, deployment and administration of Source Tree as a source Related
Platform.
 Proficient with the installation, configuration and usage of Polarion SVN Importer, Regarding
Migration from CC-SVN on windows servers.
SKILL SET
Languages Bash, Python
ConfigurationManagement Visual SVN Server3.2.0, IBM Rational Clearcase7.1.2 , Git 2.5
It Infrastructureand
Automationtools
Chef 12.2,Puppet 4.2,Ansible2.1
CloudServices OpenStack , Docker1.11
Build tools Apache Ant1.9.0, Apache Maven 3.2.2,nexus
Continuous Integration Jenkins2.2.0,Electric commander
Operating Systems Microsoft Windows Server 2003/XP/NT/2000, Red Hat Linux
Web/db Servers Apache Tomcat 7.0.42,JBOSS 6.0, Oracle DBA 11g
Code Coverage Tools Sonar4.3
Client Server Tools Tortoise SVN 1.8.10,SourceTree1.2+
Cloud Plot form Atlassian Stash(bit bucket), GitHub
Defect Tracking tools Atlassian Jira6.3.3
Validation tools Checksum1.11,Beyond Compare4.0.5,STATsvn,CommitMonitor
Migration Tools SVN Importer 1.2.SVN Mirror, SubGit 2.0.3,Migrate2SVN 2.3,CC2SVN
PROFESSIONAL EXPERIENCE
 DevOps Engineer at Infinite Computer Solutions Pvt. Ltd (14-03-2016—till-date)
 SCM Consultant at POLYCOM TECHNOLOGY (R&D) CENTRE PVT.LTD (18-05-2015---11-03-
2016)
 Application Engineer SME, WIPRO TECHNOLOGIES (03-05-2010------18-05-2015)
Educational Qualification
 Bachelor of Technology from Jawaharlal Nehru Technological University

3. Project: Operational Support System (OSS R&D) 14-March-2016- Till Date
Role: DevOps Engineer (Ansible)
Responsibilities:
 Working with engineers to design & implement deployment workflows for
dev/staging/production environments.
 Proactively monitoring overall infrastructure performance and recommend / drive the
necessary corrective measures if needed.
 Support our existing production environments and improve upon them.
 Managed and supported hosted operations, being able to troubleshoot and identify the root
cause/bottleneck with minimal supervision.
 Taking personal responsibility for the availability, scalability and reliability of our hosting
solutions.
 Able to automate to continuously define, build and deploy infrastructure by Ansible.
 Able to setup the whole Ansible environment for the continuous deployment, has done the
ansible host setup and generated the SSH public key for client configuration.
 Have placed the respective servers (like db servers, web servers, test servers and production
servers) IPaddresses to the ansible hosts file for the automation for continuous deployment.
 Have created, written and executed ansible playbooks and able to call the external commands
and have executed the both shell and python scripts using playbooks for the project
configuration.
 Able to create the roles and has written tasks, tests, templates and files and able to call all
these into the playbooks for the respective configuration.
 Have created the group_vars file to store the global variables for the ansible host-client
configuration.
 Have automated to check the OS version to see whether this is our current version or
derivatives and later.
 Have done the JDK installation through ansible host to all ansible clients and has written code
to disable the second time execution of ansible playbook.
 Have created directories and recursive directories and have created the respective users and
groups for the each installed packages like Jboss and oracle environment.
 Have Disabled the Selinux and Iptables for some security related issues , while trying to install
the 3rd party packages during installation it may cribs and sometimes we may face permission
related issues if it is enabled.
 Able to start the NTP protocol used to synchronize the clocks of Ansible nodes to sometime
reference.
 Have installed JBOSS_FSW (but if it is not already installed) using command – by parsing
templates as arguments. Jboss-fsw configurations like copying jboss-as.conf, standalone.xml,
standalone-ha.xml (with data source creation and logging update) and adduser.sh and update
standalone.xml , stopping and starting jboss, jboss service status check.
 Taking the backup of directory recursively on remote mode - ansible server.
 Have done the deployments of jars and wars in jboss application server using ansible code and
able to calculate the SHA1 value for each and every jar or war for the saved version check.

4.  Have done both standalone and HA installations in jboss and have done post install actions like
modified or updated standalone.xml, standalone-HA.xml, limits.conf, jboss-as.conf and
standalone.sh for project related variables.
 Have done the oracle installation in all DB related servers most of the percent automated and
some steps were done through manually.
 Have extensively used looping mechanism in ansible for project release related tar files to copy
and unzip in ansible nodes.
 Able to install docker machine on virtual hosts and can run docker containers.
 Able to create free floating file systems like volumes and can attach it to process isolated
containers.
 Able to setup a registry with in stores repositories and can log in, log out and search a registry
from image and can pull and push image to and from registry and local machine.
 Able to create an image from a docker file, tar ball and also from a container, can load the
image from a file and save the image, can able to perform all the operations like remove ,load,
save, history of image, tags an image to a name and clean up images in a single operation.
 Able to create and run a container and the operations like remove, start, stop, restart, kill can
be performed within the container based on project requirement.
 Able to execute the commands from a container, and export turns container file system into a
tar ball.
Project: Chief System Integrator (Polycom) MAY 2015- March 2016
Role: SCM Consultant (Ansible)
Responsibilities:
 Automates the deployments of software applications inside containers by providing additional
layer of OS virtualization using Docker.
 Have created different kind of images using Docker like user defined, base (OS) images and
dependent child images.
 Able to use the multiple inventory files at the same time those cane be static and dynamic used for
AWS and Openstack.
 Have extensively used the concept of patterns used to segregate the groups of servers.
 Able to maintain the connection between the git repositories and ansible to pull the git
repositories and for automation.
 Have used the include module to call the other playbooks or tasks into our local playbook.
 Have done the deployments through ansible for that have used JBOSS as an application server.
 Able to use the ansible ad-hoc commands for temporary execution of playbooks and
configurations not to save for future purposes.
 Able to create, debug, and run the ansible playbooks and able to trigger the specific tasks to run.
 Have extensively used Ansible-galaxy concept to create roles for organized related tasks and data
into one coherent structure.
 Have used the concept of alsible-vault to encrypt and decrypt the playbooks for security related
puposes.
 Have used the looping and array-variable mechanism to avoid the repetitive deployment of
configurations in ansible.
 Have installed the docker client on windows servers with the help of virtual box to make them as

5. clients to deploy the containers.
 For some projects we were using the vagrant and it has a utility called docker provider to
manage our docker builds and environment.
 Have used the tags module to run specific tasks in a playbook in ansible for some kind of
deployments.
 Have used the environment module to set the linux variables using ansible.
 Have used the lookup plugin that allows the access of data in ansible from outside sources.
 Have created the empty files using ansible to automate into nodes.
 Created cookbooks and wrote recipes for the configuration in chef.
 Able to automate to continuously define, build and manage infrastructure by both chef and
puppet.
 Extensively able to use the OHAI to gather system information for knowing machine status in chef
and as well as FACTER in puppet.
 Able to borrow and share cookbooks around the community with bunch of knife commands.
 Declared required resources for the desired configuration in chef.
 Able to make the configuration between chef server and nodes either physical, virtual or cloud
based.
 Able to declare the data bags to store (uid & pwd) loaded by a recipe.
 Able to manage environments with in a single organization on a chef server.
 Able to manage the nodes that are associated with one or more nodes on a server.
 Created run-list an ordered list of roles or recipes.
 Able to install chef client on the target machine with the help of boot strap.
 Able to use HAPROXY to balance the load.
 Have used cookbook build process to deliver the required builds.
 Generated cookbooks CI JOBS and RELEASE JOBS in Jenkins machine.
 Involved in Application deploy process.
 Applied manifests (puppet programs) on the local systems (Puppet agents) from the puppet
(master) server to run the puppet.
 Able to manage dependencies of resources, resource declarations and resource ordering in
puppet.
 With the use of manifests, created user accounts, installed packages and configured whole
servers.
 Created files and declared packages in manifests.
 Have frequently used puppet forge to get the modules and codes.
 Declared variables and conditional statements and facts in puppet.
 Done module smoke testing to get benefits during development in puppet.
 Have extensively used puppet file server to transfer static files.
 Securing the puppet file server consists of allowing and denying access per mount point.
 Have learned template out configuration files with puppet , filling variables from the client
system.
Client: BARCLAYS (Investment Bank) DEC 2014 – MAY 2015
Role: Application Engineer (Git Administration)
Responsibilities:
 Created Views for selected Vobs for migration in Clearcase.
 Created Repositories to store the migrated code in SVN.

6.  Created dump file and history file, then imported source code to repositories.
 Wrote test cases for System Integration testing (SIT).
 Performed Checksum between clearcase vobs and svn and Git repositories.
 Created Projects in Atlassian Stash.
 Created Repositories in Projects in Atlassian Stash.
 Performed checkout source code to SourceTree from Stash.
 Reported to a DevOps Manager, who will coordinate with teams outside of the development
group.
 Performed creation, modification and deletion of source code through SourceTree.
 Cloned remote repositories to local repositories for synchronization of code.
 Performed push and pull operations.
 Conducting or supporting the deployment of software releases into development and test
environments, troubleshooting release package, and deployment procedure or environment
configuration issues.
 Involved manual migration of code from clearcase to subversion.
 Performed manual migration of code from clearcase to Git.
 Build, manage, and continuously improved the build infrastructure for software development
engineering teams including implementation of build scripts, continuous integration
infrastructure and deployment.
 Performed manual migration of source code from Svn to Git.
 Wrote Python script for evaluating GIT CC commands for migration of code from Clearcase
to Git with history.
 Configured Tomcat application server for hosting web apps.
 Once the process KT is complete from development team, write build and deployment scripts
according to SCM team standards and processes to QA, IST, and UAT Environment.
 Retrieved all the elements associated with baseline/label to perform manual baseline migration
from clearcase to atlassian stash.
 Changed config specs of views for required files and folders associated with base clearcase
labels.
 Automated deployment process, where it copies the Jar& Ear files and starts deploying into
Tomcat Environment using Jenkins plugins.
 Created views for Integration and development streams, to fetch the elements of streams.
 Rebasing the streams according to baselines, to fetch the elements associated with baselines.
 Created projects, components, streams and child streams in UCM clearcase.
 Wrote batch script for cloning Svn repository to Git repository.
 Successfully migrated branches and tags Svn to Git although structure and behavior is
different.
 Wrote Ant Scripts to automate builds for various environments.
 Used Ant and Maven scripts for all the build scripts.
 Trained developer forChecking Outand Checking In the elements (sourcefiles) from the VOB
repository.

7.  Migrated baselines/labels in clearcase as tags in Git-Stash.
 Edited config files for path related adjustments in Svn importer.
 Documented for all possible approaches of migration from cc-svn, svn-git-stash, cc-git-stash.
 Involved in integration between Git-Jenkins.
 Created tags and branches for specified commits in Git-Stash-SourceTree.
 Resolved merge conflicts in Git-Stash.
 Supported customer for possible way usage of documents prepared by offshore team.
 Performed incremental migration for updated versions concurrently tracking changes in
source code managements.
 Enabling and disabling hooks for admin and user privileges.
 Created repositories according the structure required with branches, tags and trunks.
 Analyzed and resolved conflicts related to merging of source code for SVN.
Client: MACY’S INC Feb 2013– December 2014
Role: Software Engineer
Responsibilities
 Created VOBS, VIEWS and assigned to the base clearcase.
 Performed merging techniques to merge the source elements of different versions
 Trained developer forChecking Outand Checking In the elements (source files) from the VOB
repository
 Involved in creating Dynamic views.
 Wrote Ant Scripts to automate builds for various environments.
 Used Ant and Maven scripts for all the build scripts.
 Creating automation tool using Jenkins of SIT and UAT builds.
 Implemented Continuous integration effort with Jenkins along with scheduled builds for
Releases
 Configured various Jobs in Jenkins such that it keep tracks the changes with source elements in
the VOB repository
 Interacted with supporting teams to understand client deployment requests.
 Coordinate with the Development, Database Administration, QA, and IT Operations teams to
ensure there are no resource conflicts.
 Worked closely with Project Managers to understand a code/configuration release scope and
how to confirm a release was successful.
 Build, manage, and continuously improved the build infrastructure for software development
engineering teams including implementation of build scripts, continuous integration
infrastructure and deployment.
 Proactively seeks opportunities to implement improvements to internal development processes.
 Implemented continuous integration using Jenkins.

8.  Implemented continuous integration using Jenkins.
 Created repositories according the structure required with branches, tags and trunks.
 Analyzed and resolved conflicts related to merging of source code for SVN.
 Attended sprint planning sessions and daily sprint stand-up meetings.
 Created jobs for tagging and branching.
 Configured application servers (Tomcat) to deploy the code.
 Created and configured multiple instances on Tomcat Server for different teams.
 Configured plug-ins for the integration tool to the version control tool.
 For check in process used Tortoise SVN as a CM tool.
 Utilize Jira for issue reporting, status, and activity planning.
 Extensively used Maven tool to do the builds, integrated Maven to Eclipse.
 Integrated Maven with Jenkins for the builds as the Continuous Integration process.
 Build Java code in different Jenkins servers as per the schedule.
 When required applied patches as per the release process.
 For on boarding existing application, performing Knowledge transition from Development
team to SCM team on build and deployment process.
 For New applications, work with development team to get the requirements of application build
and deployment process.
 After complete of the scripts development and process setup, execute the builds and
deployments to all above environments based on weekly scheduled build calendar.
 Prepared and Maintained Build, Release and Deployment documents.
Client: state street bank May 2010 – Feb 2013
Role: Associate Software Engineer
Responsibilities
 In Clear quest user adding and Database permission providing.
 Configure J2EE based application to support multiple developments.
 Support code and configuration management.
 Create and maintain build, deployment and rollback scripts/tools.
 Execute scheduled application builds and deployments.
 Provide support for application and environment configuration issues.
 Coordinate with support teams to support and resolve build issues.
 Maintain code branches and coordinate code mergers with revision control utility.
 Manage, update, configure and provision development and testing environments..
 Deployments on WebSphere Application Server.
 J2EE builds using ANT scripting.
 Experience in migrating builds from ANT to Maven.
 Experience with using, administering or configuring Hudson/Jenkins CI tools.

9.  Experience of creating release branches, Labels.
 Experience of merging changes from release branch to depot and resolving the conflicts
occurred at the time merge process.
 Educate and mentor the engineering team on the organization’s build systems and processes.
 Involved in writing Ant and shell scripts for compilation and deployment process.
 Created activities and assigned to the developers to fulfill the client requirements.
 Involved in working with tomcat Deployment server admin console for deploying
applications.
 Work with teams and project managers to deliver quality software within schedule constraints.
 Communicated with all levels of engineering, management, development and test teams.
 Responsible for documentation and execution of implementation and post implementation
support plans.
 Create and maintain scripts for automating common activities.
 Conducting or supporting the deployment of software releases into development and test
environments, troubleshooting release package, and deployment procedure or environment
configuration issues.
 Automated deployment process, where it copies the Jar& Ear files and starts deploying into
Tomcat Environment using Jenkins plugins.
 Created views for Integration and development streams, to fetch the elements of streams.
 Rebasing the streams according to baselines, to fetch the elements associated with baselines.
 Created projects, components, streams and child streams in UCM clearcase.
 Wrote batch script for cloning Svn repository to Git repository.
 Successfully migrated branches and tags Svn to Git although structure and behavior is
different.
 Wrote Ant Scripts to automate builds for various environments.
 Used Ant and Maven scripts for all the build scripts.
 Trained developer forChecking Outand Checking In the elements (sourcefiles) from the VOB
repository.
 Migrated baselines/labels in clearcase as tags in Git-Stash.
 Edited config files for path related adjustments in Svn importer.
 Documented for all possible approaches of migration from cc-svn, svn-git-stash, cc-git-stash.
 Involved in integration between Git-Jenkins.
 Created tags and branches for specified commits in Git-Stash-SourceTree.
 Resolved merge conflicts in Git-Stash