Interview: Phone and skype
Description:
Moving Logix Designer Builds to a Single MS Build based Build System:
Today we have desktop builds using MSBuild (Visual Studio) and Build Machines using Omake (ClearCase Build System) – these is a big productivity drain, engineers are maintaining two build environment for every change, causing constant build breakages and lot of maintenance overhead. We need to maintain expertise and technical understanding of both MSBuild and OMake.
This also prevents us from moving to CLM as OMake is tied to Clear Case and so are many of our builds Scripts. In addition Having a big Monolithic Build System is preventing us from moving to a more incremental (build what changed) model as well.
Ask: 2
With this investment we would do following..
• Have a single build environment based on MSBuild. Vastly reducing build failures and improved productivity.
• Set up subsystem dependencies so that we can parallelize builds and potentially get to incremental builds (build only what changed rather than all 4 million lines of code). This gives us faster build times, moves closer to CI (real time builds), Once something is built and tested, we do not build and test that component again unless it's changed – better test outputs.
• Sets us up for managing external dependencies via MS Package rather than build scripts. This gives us predictable, automated Bill Of Materials, new components (internal and external) are integrated automatically, vastly improving our ability to consume and understand what component set we are building with.
• As we shift our focus to build unit tests – having consistent MSBuild Based environment means we would be able to run Unit tests on dev boxes and the whole set in our CI Servers at desired cadence.
Designs, defines, architects and develops system enhancements and new products. Develops software, interfaces, and/or architecture for complex features. Typically requires 5-7 years of experience.
•
Last updated on May 31, 2017