Submitted By Jenkins User Thomas Haver
Consumer bank modernized their legacy system to event-driven architecture with help from Jenkins pipelines and plugins.
Programming Language: Java, C+
Platform: Android, iOS, Docker or Kubernetes, MacOS
Version Control System: GitHub, GitLab
Build Tool: Maven
Community Support: Jenkins.io websites & blogs, Networking at Jenkins event
From monolith to modern in event-driven consumer banking.
Background: Our work environment was a giant monolith built on Corillian Voyager, a software platform combined with a set of applications for Internet banking, electronic bill presentment and payment, targeted marketing, data aggregation, web content management and online customer relationship management. In order to modernize and switch to event-driven architecture, we had to pull Voyager apart bit by bit.
Goal: New architecture.
Solution & Results: We used Jenkins for test automation to confirm changes to the current stack and ensure that the nextgen stack would not hurt functionality. The plugins we relied on most were the Pipelines and the Cucumber reports.
Cucumber is a test automation tool following the principles of Behavioural Driven Design and living documentation. Specifications are written in a concise human readable form and executed in continuous integration. It allows Jenkins to publish the results as html reports hosted by the Jenkins build server. To get it to work, you must be using the JUnit runner and generating a json report. The plugin converts the json report into an overview html linking to separate feature file HTML with stats and results.
Jenkins made it easier to scale our work and handle parallelization without headaches. We all became Certified Jenkins Engineers in the process.
Our results showed improvements in: