Build and Integration Engineer Resume

Work Experience:

Confidential

Build and Integration Engineer

Responsibilities:

Moving the Developer Code into a Customer Build.
- Making a test build (using CI tool or local Linux workspace) with features/bug fixes for QA
- Detecting merge conflicts, compilation errors
- Merging commits to mainline though CI (followed by approvals)
- Getting open source and security approvals
- Tagging commits and Releasing the Build
- Making various customer builds and pushing the open - source content to the Code Aurora Forum
Using repo/git/gerrit, and Linux machine via SSH
Android 5.0 Lollipop AOSP bring-up for Confidential chipsets
Source Code Management (git-repo, TortoiseHg): Branching/Merging/Maintaining branches
Code Review Tool (gerrit): Integrated with CI tool. Uploading code patch-set in case of merge conflict, rebase conflict, setting inter-project dependencies for proper testing in CI, and going through several approvals and rules before merging commit into branch.
Software Build Management/Continuous Integration Tool (Electric Commander by Electric Cloud): Using automation tools for daily tasks (Internal/External Builds, CAF push, gerrit tasks, changing CI methods)
Python/Shell: Writing scripts to avoid manual/mundane tasks, automating Linux (shell) processes with python.
Change Management System (PRISM): Managing code Change Requests and Security Fixes
Issue Tracking (JIRA): Creating project branches, Managing Automated Build Schedules, Managing Open Source/Proprietary Approvals (for external release)

Confidential

Intern/Product Development Engineer

Responsibilities:

Confidential

Build and Integration Engineer

Responsibilities:

cdp: Wrapped around repo, it opens the project path from the project name.
cdg: Wrapped around gerrit query, it opens the project path from the gerrit number.
push: Generates and executes (optional) the git push command from any project.
Gerrit Filter: Parses gerrit number from the input string. Removes the duplicates and outputs the gerrit numbers in a linear fashion (optional, for Electric Commander) along with the count of commits.
Change Propagation: Queries each gerrit for change id (filters out the merge commits), queries the change id and stores the gerrit from the input branch in a list. Outputs as 1. Gerrits not propagated 2. Gerrits Propagated 2a. Gerrits Merged 2b. Gerrits not merged.
Project List: Parses the default.xml file and groups the projects by revision
Gerrit Log: just like a git log, this outputs a log with gerrit link and commit message.
Gerrit Tree: User inputs a gerrit (not merged), the scripts traces back to last merged commit, and traces forward the ‘needed by’ and saves as tree/multiple trees. Also helpful to retrieve the end merged/unmerged commit for git check-out.
hy11 equivalent: Copies the build details from one filer location and searches for the same file in another filer location, to get an equivalent build.
hy11 rename: Renames the build folder with a user preferred prefix followed by a time stamp.