Build/Release/CM Engineer Resume

OBJECTIVE:

Looking for a challenging position in Software Configuration Engineer or build/release Engineer.

TECHNICAL SKILLS:

Unix Programming: Perl, Bourne, Korn and C - shell, Sed and Awk

Tools: Configuration Management: Perforce, Jenkins/Hudson, BuildForge, CM Synergy (Continuus), Change Synergy, Problem-Tracking, Bugzilla

Software Development: Gnu, Crystallize4.0, gcc, gc, g++ Software automation (build/test/packaging): Maven, Ant, Make, gmake.

Database Software: MS Access, Visual Basic

Operation Systems: Sun-Solaris, CED, X-Windows, Window-NT,Window, DOS, various network andCommunication managers (e.g. TCP/IP)

Languages: C++, Perl, SQL

PROFESSIONAL EXPERIENCE:

Confidential

Build/Release/CM Engineer

Responsibilities:

Using Perforce as Version Control to Manage-branching, tagging, merging and diffing codes between branches.
Playing Admin role in Perforce to add, remove users & manage table’s protection.
Configures builds via Jenkins/Hudson, administers production build servers
Builds and compiles codes on both Linux and Window base operating systems.
Administer, generate & trouble shoot license issues for both QA and Partners.
Manages and facilitates release planning: Facilitates development team coordination, prepares production artifacts, tracks releases for historical
Delivers relevant reports regarding changes within the SCM domain
Using Bugzilla as bug tracking tool to report, and keep track of defects.
Communicate with developers as well as QA to make sure builds and tests go smoothly

Confidential

Build/Release/CM Engineer

Responsibilities:

Utilize the Perforce command interface to automatically pull source code for builds
Manipulate BuildForge to put together automated environments for building multiple baselines, resulting in an easy to deploy production-ready package.
Perform branching, integrating, merging, and check-in/check-out sources codes.
Write Perl scripts to automate builds, schedule builds, maintain build software, hardware, and apply Patches.
Monitor hardware, report and schedule repair, diagnose and correct build problems
Implement build system changes addition of new tools and applications
Diagnose bottlenecks to the build system and suggests changes.
Promotion through idjit to Alpha, Beta Environment
Write document procedures and release notes.

Confidential

Software Configuration Management Engineer

Responsibilities:

Provide CM to development team
Maintain and publish product revision history and ensure that product software is traceable back to the source and environment that produced it
Create, maintain, and control build scripts, build environment and build procedures used to create software products
Create, maintain and control build smoke test suites and equipment
Perform builds, execute smoke tests, document results and publish software with build notes
Provide build metrics to management and SCM team

Confidential

Software Build Engineer

Responsibilities:

Responsible to interface with Engineers and Operations to establish and maintain the software development structure using Continuus/CM tools on UNIX and PC.
Performing builds, verifying builds against testing suites.
Write scripts to automate some builds.
Design and implement build processes for different products.
Create and track the release of products as well as the patches.
Maintain the integrity of Revision Control repositories
Troubles shoot and generate the release notes.
Maintaining software CM status accounting, and generating software CM baseline documentation and media.
Train developers in proper use of Revision Control System (Continuus and Problem Tracking Tools)