Situation

1. For one of our clients, Build is taking 8 hours and nightly build is failing frequently.
2. Test case execution is consuming more time than the compilation.
3. Low confidence levels for developers on nightly builds and subsequently during integration cycle.

Approach

1. We reviewed the whole set of build scripts being used and test case suite to check how we can refatcor them.
2. Verified the build infrastructure i.e., build server capacity from hardware point of view.
3. Feasibility study done to check how a CI environment help in giving faster feedback on the quality.

Solution

1. Refactoring done for build scripts to make modules compilation parallel (wherever possible).
2. Some test cases are selected (which don’t require external services like database) to run as part of the build.
3. CI environment (using open source cruise control) is established to run builds per commit and execute only above set of test cases as part of the build.
4. Set up low-cost remote agent machine which will run remaining test suite once per day.

Results

1. Build took only 1 hour and gave faster feedback to dev team.
2. CI environment provided good confidence to dev team.
3. Team is able to implement more best practices.
4. Effective use of existing build  infrastructure (hardware) ensured no further cost is required.
5. This helped the client in ensuring smooth release management.

• Author
• Recent Posts

scmgalaxy K

Latest posts by scmgalaxy K (see all)

• Use of runtime variables to save into another variable using register in Ansible - September 6, 2018
• Ansible & Ansible Tower Variable Precedence Hierarchy - September 6, 2018
• How to use template in Ansible? - September 6, 2018