Nisum implemented a CI/CD framework that allowed developers to input their own pipeline requirements and increased their bandwidth for developing new features.
The number of ad hoc requests received daily was drastically reduced, allowing the client to have a smaller team that can focus on the implementation of new features. The change ratio is:
80%
|
|
30%
|
20%
|
|
70%
|
Business Challenge
A Fortune 500 grocery client had outdated practices that created a poor division of roles that were counterproductive from a DevOps perspective, so developers were not involved in any aspect of the pipeline definition, implementation, or maintenance, leading to:
-
Every pipeline change or error needing to be addressed by the DevOps team, which led to:
-
An unscalable DevOps team size
-
Waste of resources
Solution
Nisum implemented a CI/CD framework that was easy for developers to use and input their own pipeline requirements. They also created a product manual to inform and train the developers on the use of the framework, resulting in:
-
Reducing tasks for the developers by defining reusable pieces of code to handle repetitive Jenkins pipeline tasks. They accomplished this by encapsulating the whole pipeline logic to use the Jenkins shared library plugin.
-
Reducing repeated work and refocusing resources by enabling developers to write and define their own pipelines, from within their source code, by using a shared library achieved by:
-
Creating a flexible and simple Jenkinsfile DSL and using an agile method for the implementation process with a QA pipeline. They tested changes and different test environments for the CI of the shared library. External services were integrated into the shared library to make it easy to use. These services included Artifactory, Sonar, PCF, Azure key vault, and Veracode.
Feel free to contact us for more information on how Nisum can drive results for your company.
