SUMMARY

• Senior Configuration, Build and Release Manager offering an extensive background including over 20 years of applied expertise utilizing Unified Change Management (UCM), Change and Release Management, Version Control and Build Support/CM Processes.
• Additional background includes advanced working/supporting knowledge of ClearCase, Rational Unified Process (RUP), Perforce, CVS, RCS, VSS, TFS, GIT, Java, and ANT.
• Results oriented professional with exceptional problem solving abilities and communication skills.
• Currently involved in performing integration in Orchestrator workflow management solution using PowerShell to automate Dev - Ops related procedures.
• The processes include Builds/Deployments/Full QA support, in an automated manner which no human interaction would be required.

PROFESSIONAL EXPERIENCE

Confidential

Sr. Build Master

Responsibilities:

• Prepared documentations on Branching (P4 Stream) methodology
• Prepared documentations Build & Deployment using Jenkins definition and P4 Stream.
• Prepared documentations on binary asset and to support multiple environments such as Dev/QA/Prod.
• Created and used P4 Stream using different path types such: share, isolate,, import, import+
• Import+ was used and implemented to accommodate different types of file formats such all types binaries (.dds, .swf…etc) with Freestyle Multi-job and Parallel Multi-job plugins in Jenkins.
• Maintain and support Jenkins for Post-deployment issues in CI/CD manner.
• Used Jira & Confluence extensively for bug tracking and story/task tracking.
• Attended and setup up daily meeting and agendas for the current and next spring.
• Modified existing Python/Perl scripts and added new ones as required in the CI/CD processes.

Confidential

Sr. Software Configuration Manager

Responsibilities:

• Maintain multiple source repository, Source control system (TFS) and branching.
• Build & Maintained Applications including SaaS (Software as a Service) applications models.
• Automate the build using a cloud version of visual studio to simplify continuous integration of appsfor platforms and programminglanguage used. Visual Studio Team System (VSTS) using GIT version 2.10.0. Windows.1.
• Visual Studio Team System (VSTS) is an extension of the Microsoft Visual Studio architecture that allows it to encompass development teams, with special roles and tools for software architects, developer specialties, and QA. Visual Studio is a software development environment built on the.NETFramework that is designed for managing projects and development work in a variety of languages including Visual C# .NET,andASP.NET.
• VSTS integrates with the Team Foundation Server (TFS) through a TFS ClientAPIthat exposes Team Foundation Server functions. These include a Team Explorer for browsing and managing items in team projects and a Source Control Explorer that provides version control, revision handling, and check-in/check-out functions. VSTS can use the Team Build system rather than its own built-in build system, and the same reporting IDE that enables inspection and analysis of VSTS elements may be applied to the Team Foundation Server and its contents as well.
• Run Smoke testing upon each deployment.
• Every commit should build on an integration machine.
• Keeping the build fast.
• Test in a clone of the production environment.
• Make it easy for anyone involved to get the latest executable.
• Automate deployment
• Supporting/Maintaining Development Environment as well Test/Production ${env}.
• Run multiple Builds/Deployments onto Test/Staging/Production Environments.
• Using SpaceRack (to maintain to force down/up a server in load balancer)/Octopus 3.0/SaberSwitch (change environments to point from one to another for QA testing) /Visual Studio Team System (VSTS) using GIT version 2.10.0. Windows.1 for Builds/Deployment processes.
• Maintaining and coordinated weekly Build/Deployment Plans/Deployment Schedules for all releases (Major/minor).

Confidential

Sr. DevOps / Software Deployment

Responsibilities:

• Upon completion of the sale, expected to close at the end of the year, Confidential will become a privately held company.
• This development will give both Symantec and the Confidential business the financial wherewithal to accelerate the execution of their respective strategies and bring innovation to market sooner for partners and customers.
• Joined Confidential while the separation from the technical aspect was still in progress, as a specialist responsible for Master Perforce Server and NINE sidetrack server for SSL connections.
• The deployment maintenance of replica servers into remote sites.
• Depending on the network configuration, these remote sites have highly secure communications pathways back to the master server, such as that provided by a Virtual Private Network (VPN), and in addition maintaining over 5000 P4 users for the company.
• Sr. Software configuration management to take over the existing build and release processes and environments mainly using a variety of products in addition to Perforce.
• Used Python 3.4script for the various purpose including build/release.

Confidential

Sr. DevOps / Software Deployment

Responsibilities:

• Coordinating and scheduling software releases from internal engineering to production systems recording change execution to comply with SOX, FDA, CLIA (Clinical Laboratory Improvement Amendments) and other auditing requirements
• Proposing and implementing process and Perforce/VSS improvements related to Configuration Management and Application Deployment.
• Took ownership of Source control system (VSS/Perforce/TFS) and implemented branching methodologies.
• Take ownership of the release and deployment processes, helping to shape deployment scheduling decisions and ensuring that change is properly monitored and recorded.
• Provided consultative services to the larger organization, recommend deployment/installation solutions, develop and guide teams toward a common deployment framework and toolset.
• Driving cross-functional automation initiatives that improved the productivity and effectiveness of the organization.
• Deliver high-quality product consistently on, ahead of, schedule.
• Constantly “move the ball forward” with respect to process automation/reduction in repetitive tasks.
• Continuously look for (and implement) opportunities to simplify and streamline processes, and propose concrete solutions with a plan for implementation that fit within my sphere of influence.
• Guided direction only in complex situations and handle routine, and even moderately complex, situations while advising high-level management - but not requiring management prioritization / assistance at every step.
• Solve routine problems quickly/efficiently.
• Subject matter expert in my area(s), and actively promoted best practices across the organization.
• Self-managed day-to-day task priorities/time allocations, and advise higher level managements of exceptions in a timely fashion, to ensure that I was an enabler.
• Currently involved in performing integration in Orchestrator workflow management solution using PowerShell to automate Dev-Ops related procedures.
• The processes include Builds/Deployments/Full QA support, in an automated manner which no human interaction would be required.
• Getting the environment ready to move into the Salesforce1 cloud.
• Working with Jenkins for continues integration purposes 1.6 on Windows 2018/2012, External Job were used which allowed logging the executions of processes outside of Jenkins, even on a remote server.
• This model was used so that we could use Jenkins as a dashboard for our automation system.
• Java SE development Kit 8u77 as one of the needed plugins. Perforce 2015 was also used to pull source codes over to build environments.
• Builds/Deployments were done with Jenkins 2.5

Confidential

Sr. DevOps/Software Build & Release Manager

Responsibilities:

• Design and administer Visual Source Safe (VSS) and its branching methodologies, Build & Release Automation for the full/incremental/patch build in an active/web based Windows environment to support the development and deployment life cycle fully.
• Maintaining complex .NET development environments to accommodate the constantly changing codes for 32 Web Servers.
• The inherited VSS processes were/completely modified to accommodate better and more reliable environment.
• Ultimately migrated from VSS to Perforce 2004 on the company’s network to support R&D successfully without any loss of data based on my own recommendations.
• Setup full build/deploy environment under Perforce for support all development life cycle.
• Continue to support and improve build/deploy environment for more powerfully controllable and powerful environment.
• It is now at a stage which is controlled and monitored remotely.

Confidential

Sr. DevOps / Software Build & Release Manager

Responsibilities:

• Implemented configuration management, release procedures, and worked with Servers using Perforce 99.2.
• Implemented branching methodologies under P4 for the associated repositories.
• Developed/used tests & build scripts as required including assessment of software system based on cross-platforms.
• Completed build test status and tracking documentation in an accurate and timely manner for several versions of software on NT Servers.
• Performed setup and used Perforce 99.2 in release life cycle. Utilized of Microsoft Visual C++ 6.0 compilers in release life cycle.
• Supported and maintained and executions on internal servers. Installed and used MKS Toolkit to convert NT server into Solaris platform to use Unix/Linux Utilities and Perl 5.0 for Build, Release and Deployment process on an in-house built in on LAMP & other (SaaS) leveraging JBoss, Linux, MySQL,iSCSI, NAS, SIP, products.
• Installed/Used MKS Software provided automation and interoperability solutions for developers and system administrators.

Confidential

Senior Configuration Management Specialist

Responsibilities:

• Dimension8.0 administration, build & release automation for the full/incremental/patch/branching methodologies build and Releases/Deployment processes on the designated AIX servers for DB/APP in a Retek environment.
• Maintaining complex AIX environments to accommodate the changing Retail requirements for W&S applications.
• Supported/maintained PVCS 6.5/8.0 integrated Tracker and Test Director Interface administration.
• On DB side administered/executed SQLPLUS application; inserting/dropping/adding rows, etc. by using TOAD and SQLPLUS command line interface.
• Apache ANT 1.6. X UNIX utilities Pearl 5.x were used for complete build/release processes implemented/maintained/supported by me.

Confidential

Senior Configuration Management Specialist

Responsibilities:

• Implemented entire CM processes as well as performing administration of Clear Case involving Unified Change Management (UCM) of Rational Software for all existing products. Designed and documented CM plans including branch methodologies.
• Established processes and implementation of CM plan. Designed/implemented Build Processes and supported implementation of build processes for four products.
• Collected, compiled, and tested source codes to produce final cohesive product all the way to production sites.
• Provided support and maintenance of IBM Web Sphere Studio Developers for Windows version4.0.3 application.
• Installed, supported, and maintained headless Ant 1.3 all for component compilation. Installed, supported, and maintained DJ Java Decomposer 3.2.
• Handled creations and maintenance of five separate repositories (VOBs) under VOB database schema version 54 of Unified Change Management (UCM) of Rational Software. Maintenance of SQL files and DB processes, in general, using SQLPLUS were a major part of my responsibilities.
• Due to the complexity of the ClearCase usage for end-users (R&D/QA Teams), recommended Perforce for implementation to replace ClearCase.
• Transitioned from ClearCase to Perforce and provided complete Perforce admin setup.
• Completed configuration management/release procedures, and owned servers using Perforce 99.2.
• Developed and executed tests and build scripts as required including assessment of software system based on cross-platforms.
• Took charge process of managing change in development from requirements to release.
• Under Perforce 99.2 the development life cycle, defined change management to requirements, design models, documentation, components, and source code.

Confidential

Senior Configuration Management Specialist

Responsibilities:

• Installed, maintained, and supported Visual Source Safe with PVCS for Configuration Management processes.
• Performed migration from VSS to PVCS using PCLI, and developed scripts to ensure migration processes took place within safe and timely manner.
• Implemented Branching methodologies under PVCS.
• Used Samba to implement PVCS connectivity.
• Supported web based Java product involving Visual Source Safe/PVCS. Installed and used MKS Tool kit to convert NT server into Solaris platform with Unix Utilities and Perl 5.0 for Build and Release Deployment process. MKS Software provided automation and interoperability solutions for developers and system administrators.
• Developed and used PCLI (PVCS utility) and Unix Utilities/Perl for cross-platform build scripts. Utilized JDK1.2.2, JDK1.3.0, JDK1.3.1, and MAKE compilers in release life cycle. Recreated incomplete build and deployment processes on Solaris5.7 NT5 using Shell and Perl.

Confidential

Configuration Management Lead

Responsibilities:

• Maintained and supported StarTeam 4.0 (StarBaseTools) for Bug Tracking and Source Control Management processes.
• Enhanced and improved branching system under StarBaseTools.
• Developed, executed, and built release scripts using UNIX utilities and Perl 5.0 as required assessing software system based on cross-platforms.
• Completed all builds test status and tracking documentation in an accurate and timely manner for several versions of Confidential software on NT.
• Completed and owned Configuration Management Build and Release procedure SCM Servers. Performed extensive usage of JDK1.2.2, JDK1.3.0, and JDK1.3.1 compiler in release life cycle.
• Installed and used MKS Toolkit to convert NT server into Solaris platform with Unix Utilities, Perl 5.0 for Build, and Release Deployment process.
• MKS Software provides automation and interoperability solutions for developers and system administrators.

Confidential

Release Manager

Responsibilities:

• Developed and executed the test and build scripts as required. Assessed software system based on cross-platforms using Perforce 99.2 as SCM.
• Implemented and maintained branching methodologies for Perforce repositories.
• Completed all build, test status, and tracking documentation within accurate and timely manner for fifteen versions of software on NT.
• Performed setup and used Perforce 99.2 in release life cycle.

Confidential

Release Manager

Responsibilities:

• Developed and executed build and release scripts as required assessing software system based on cross-platforms, and completed all builds using UNIX utilities and Perl.
• Tracked documentation in an accurate and timely manner for several versions of software on NT.
• Completed and owned Configuration Management Release procedures and worked with Servers using Visual Source Safe (VSS).
• Setup and use Visual Source Safe (VSS) in release life cycle. Performed live installation and deployments on NT Servers.
• Supported and maintained “JADE” and “JRUN” Services for Software Compilation and execution on 10 internal/external servers.

Confidential

SR. Configuration Management Specialist/Release Manager

Responsibilities:

• Wrote/enhanced builds scripts using Perl and UNIX utilities on QNX (Canadian Version of UNIX) & NT.
• Attended Perforce Training Classes for system architecture and user interfaces and branching methodologies.
• Understood depots, workspaces, and client view maps.
• Worked with basic user operations involving the creation of workspaces, and change lists, submission of change lists, and assurance of workspaces being sync with the depot.
• Performed parallel development by merging files and resolving files conflicts.
• Used Perforce GUI/Command line interface.
• Handled branching and code line management by the creation of branches and integrating changes between branches by using named branch views.
• Worked with user protections and access permissions. Handled process support with change lists, jobs, review markers, and change review daemon.
• Performed perforce metadata-reporting techniques.
• Handled system administration, installation, resource management, database checkpointing, and recovery.
• Performed troubleshooting and error recovery. Completed and owned Configuration Management procedures and Servers using UNIX utilities with Perl.
• Created and performed nightly builds for QNX, UNIX, NT, 95, and 98. Underwent continued training for Client/Server Model, Client Programs, Change lists, Client, and Workspace at Perforce headquarters.
• Enhanced and wrote required scripts using Perl, Shell utilities for CD/Floppy cutting for product release to Product Validation and Manufacturing.

Confidential

Configuration Management Engineer

Responsibilities:

• Set up the complete environment for CM using SCM tool (CVS 1.10). Enhanced, debugged, and installed “Gnats" bug tracking system (CGI/Perl Based Gnats).
• Installed and setup CVS1.10 (Concurrent Version System). Worked to control and manage developer access to source codes based on CVS 1.10.
• Collected entire source codes from CVS 1.10 for a given release of a product into a single area for revision control system.
• Compiled source code and products binaries and libraries using CVS 1.10.
• Made source/object codes from CVS 1.10 available within the company to those using it to develop new codes.

Confidential

Configuration Management Specialist

Responsibilities:

• Collected and compiled testing source codes to produce the final cohesive product. Responsibilities for performing this function were within Configuration Management (CM) group. All processes were executed and maintained using RCS as SCM.
• Controlled and managed developer accesses to source codes on RCS. Master source for Confidential Systems products was owned by CM and lent to developers for modifications.
• Collected all source codes from RCS to release of product into a single area and assured area contained correct revision of all source codes at all times.
• Compiled source code and products binaries and libraries sent to the customer (after being tested by QA).
• Handled average transition of codes from development through SCM tool (RCS) to the compilation, testing, and manufacturing for production.
• Made source and object codes available from RCS for within company to those using it or developing new codes within it.