SUMMARY

• 11+ years of IT Experience in Source code Configuration Management, Build Management, Change Management and Devops
• Taking care of Source code management system. In - depth knowledge of Perforce. Installation, Configuration, Design and Administration, plus experience of extending and integrating these tools with rest of development environment, Repository management, Branching, Merging, Apply label, User account management etc.
• Taking care of build environment, Build tools, Home grown tools/Scripts, Continuous Integration
• Supporting all development toolset like code review tool, Defect tracking tool, Static Analysis tool, Build Acceleration tools etc
• Streamlining process, metric/data reporting to management for easy decision making
• Focus on CI/CD
• Strong ability to provide automation to existing CM process flow. Skilled in designing effective planning for SCM
• Efficient in working closely with teams to ensure high quality and timely delivery of builds and releases.
• Supporting Agile as well as waterfall development models
• End user training
• Highly motivated, organized, flexible, team player with ability to work individually

TECHNICAL SKILLS

Languages: Bash, Shell Scripting, Perl, C++, C

Operating Systems: Centos,, Linux, Windows

Code review tools: Review Board, Code Collaborator, Crusible

Databases: MySQL

Continuous Integration: Jenkins

Version Control: Perforce, GIT

Change Management: Jira, Bugzilla

SDLC/Project Mgmt: Agile Methodologies, Scrum Process, JIRA

Code Static Analyzer: Coverity, Cpp check, Lint

Build related: make, distcc, Electric Accelerator

PROFESSIONAL EXPERIENCE

Confidential, Sunnyvale, CA

DevOps Architect

Responsibilities:

• Mandating code review using Crucible
• Mandating Submit data that includes valid defect number, Unit test info etc
• Once changes are ready for submit, let developer shelve changes and we take that shelve to our build for and do sanity build and smoke testing using Jenkins and once all look green, we submit those changes on behalf of developer. Else we bounce back those changed to developer pointing at the failure.
• Do regular (3 times a day) builds and sanity in the branch for more stability.
• Push changes from stabilizing branch to release branch once a day if things look good for the day and run more rigorous testing in release branch.Swarm:
• Comprehensive comparison study of code review tool being used and come up with recommendations. As a result setting up swarm, integrate it with Jira, integrating it with Jenkins so we can achieve pre-check-in code build and sanity.Perforce:
• Triggers for not to submit unmodified files
• Scripts that give report of what is not merged from release branch to mainline (take care of even double commits instead of cherry pick) Scripts for merging changes from one branch to another as original author
• Upgrade from 12.2 to 14.2

Confidentia

Principal Release Engineer

Responsibilities:

• Setting up servers, replication, proxies, check pointing, backup, upgrades, DR plan, end user training, support etc - completely responsible for taking care of configuration tool for the organization.
• Perforce integration with Bugzilla using P4DTG.
• Trigger to avoid submitting *unchanged* files, triggers to watch submit to old releases and ask developer/manager to merge them to new release, trigger to annotate bugs form one branch to another as part of integration, trigger to enforce including bug details during submit to make sure it is ASSIGNED state at least, trigger for submit template with more info, trigger to avoid submitting unchanged files, trigger to avoid creating clients with full depot mapping.
• Managing home-grown tools for doing builds and managing about 30 build servers.
• Introducing and setting up Jenkins to the organization with continuous builds and tests
• Automation of updating certain fields in bugzilla on every submit and on every build to reduce developer manual work and streamline the process
• Statistics reporting to management about bugs incoming trend, fix trend, Customer reported bugs trend and weekly reports etc
• Alerting system for Customer reported bugs
• Coverity evangelist to the organization starting from recommending and convincing management till making sure coverity defects are being addressed and voluntarily fixing
• Evaluating and setting up Review Board
• Writing wrapper script around "rbt post" that records generated review id into perforce change list so that can be used for mandating review requests
• Writing perforce trigger that mandates review and pulls in review metadata back into perforce

Confidential

Lead SCM Engineer

Responsibilities:

• Setting up new perforce server/depot based on project needs
• Setting up read only instances for load balancing and performance improvements.
• Server, Proxy, Client upgrades
• Replication and failover for better performance and business continuity.
• Backup and check pointing.
• Triggers, Automation and Audit scripts to set policies and ease the day-to-day task.
• Work with Perforce team in getting licenses, issues and troubles fixed, beta testing etc
• Supporting thousands of people from India, USA, China, HK, UK, Russia etc.
• Providing companywide training

Confidential

Lead Release Engineer

Responsibilities:

• Define and developing the integration process and tools that fits to all Business Units
• Execute Integration to business critical releases.
• Continuous support to people doing Integration at Confidential .
• Forming the team in India and US including hiring and train and guide them.
• Responsible team lead, mentor and guide them when get stuck with problems
• Work closely with cross functional team to keep the codeline and process clean
• Tools used: Perforce, Defect tracking system, Review board, Ticketing system, Coverity, Lint etc

Confidential

Release Engineer

Responsibilities:

• Providing code merge to business critical releases
• Merge tool automation using clearcase and perl
• Release Planning and Program management
• Training and Presentations
• Leading Release Team in India
• Mostly having fun with what I do
• Tools used: Clearcase, Defect tracking system, Review tool, Static Analyzer

Confidential

Application Developer

Responsibilities:

• Design and coding using UML and C++ (Kabira Action Language)
• Release and Support
• Developed couple of server side applications for telecommunication industry using LDAP, Message Queues