The Client

A global leader in payments and financial technology.

Project Requirement & Challenges

Our client wanted to have an end-to-end DevOps implementation for data spanning across different regions. The code sited on a different region and the actual data centre were in a different region. To stitch end-to-end dev ops with compliance, security and no-delay deployment, was achallenge.

The biggest challenge involved here was to design a system to have proper handshakes between regions on secured channel.Moreover, the challenge is to convince the respective enterprise teams to open ports with a performance bottleneck in place.

Our Solution

As part of Technology team, we implemented a cross-region CICD Pipeline which spans across various components each of which plays a vital role.

Continuous Integration:

• Multibranch pipeline jobs were created withinJenkins [North America] instance which has Web hooks configured at the Bitbucket [North America] to identify commits and trigger jobs correspondingly.
• The jobs were configured on the basis of “Jenkins File”, a progressive approach in continuous integration and delivery.
• “Jenkins File” is stored as part of the code branch repository.
• This Jenkins files triggers the corresponding job which in turn cleans, compiles, installs the maven build and pushes the artifact to NEXUS [Artifact repository].

Continuous Delivery:

The linking between North America and APAC- India environment is stringent and bounded by firewall rules and hence pose a challenge with respect to connectivity and reliability. To overcome we have proceeded with “Daisy chaining Jenkins instances in North America and APAC”.

What does it mean?

• The North America Jenkins job on a successful build sequentially triggers the corresponding jobs in APAC which runs on a Jump / Bastion server within APAC Infrastructure.
• The trigger is sent with an envelope with the required details to the corresponding address.
• Post receiving the envelope, the APAC job opens pulls the corresponding artifact from NEXUS [North America] and creates a local repository for versioning / deployment.
• Once the artifact is available, we have relevant scripts to address corresponding package to be deployed with all the dependencies addressed.

Output

This approach has enabled us to completely automate the deployment process and have a streamlined approach for continuous integration as well so as to enable application development teams to deliver code changes more frequently and reliably.

This design approach has ensured there is no additional performance overhead on the existing servers and the systems are very well organised to deliver. No impact to the existing working model that was existing a decade ago.