Business Challenge
One of the most challenging tasks faced by our client was in the field of continuous integration while onboarding the partners.
- Manual build, testing, and deployment of integration code was a time-consuming process and had dependencies on skilled resources to perform the actual work.
- Developers frequently missed to check-in the files to SVN (Subversion) and deployed the wrong version to production that led to rollback and re-testing.
- Manual regression testing took time for even small changes.
- Emails were used to track deployments.
How Avasoft helped?
We understood their pain points and did the following to help them beat the manual process:
- We configured SVN, Jenkins, and Maven for continuous integration/build.
- Then we changed the process and automated the flow to trigger the build only when the code is checked in to SVN.
- We automated the build to get unit tested itself with multiple test scenarios based on the flows configured in the maven solutions and then automatically get it deployed in the target environments when there are no errors.
- We also recommended to break the work and commit them early. Though they accepted it, they were wondering how this could be a turn-key solution.
Tech Stack
Value Additions to Customer
The process automation using Jenkins and Maven saved 80% of their resource’s time and made them more focused on the core tasks.
- Automating the workflow to trigger build only when the code is checked in to SVN, saved 65% of the time that was unwantedly spent on re-testing.
- Codes are checked in to SVN and are available to peers for review. This helped them to resolve conflicts at an early stage.
- Since we automated the testing process, manually done regression testing was no more/very less needed.
- As per our recommendation, they committed the code at an early stage and witnessed a great reduction in the integration costs.
